Re: [csswg-drafts] CSS WG wiki hosting (#13504)

## Concrete proposal for a replacement 

https://w3c.github.io/csswg-wiki/

### How this proposal addresses the requirements

1. _Don’t break any existing [wiki.csswg.org](https://wiki.csswg.org/) URLs._

   Add to the csswg.org DNS these records:

   ```
    _github-pages-challenge-w3c.wiki.csswg.org.  TXT    "ca0fc182a3415a7e96abb943bcc587"
    wiki.csswg.org.                              CNAME  w3c.github.io.
   ```

   https://github.com/w3c/csswg-wiki already has `wiki.csswg.org` configured as a GitHub “Custom domain”; so, once the DNS for wiki.csswg.org has those records, [wiki.csswg.org](https://wiki.csswg.org/) will serve its content from [w3c.github.io/csswg-wiki](https://w3c.github.io/csswg-wiki).

2. _The source for the content must continue to be “web editable” in some way similar to how it’s currently “web editable”._

   Every page served from https://w3c.github.io/csswg-wiki has en <kbd>Edit</kbd> button. Pressing that button opens up the GitHub web UI for editing the source of the page directly over the web, within a browser. That mechanism is functionally identical to the mechanism currently used by https://wiki.csswg.org/.

3. _The source for the content must be some flavor of Markdown. Users must not have to directly edit the content as HTML._

   All https://w3c.github.io/csswg-wiki sources are Markdown files in version control in https://github.com/w3c/csswg-wiki.

4. _There must therefore be some mechanism which generates/publishes HTML output from the Markdown sources._

   The published https://w3c.github.io/csswg-wiki HTML content is generated using Jekyll through GitHub Pages.

5. _There must be an authentication/registration means to control who can make changes, and log who made which ones._

   - Users must be logged into GitHub to edit the https://w3c.github.io/csswg-wiki content.
   - The repo maintainers (e.g., CSS WG chairs, team contacts, other trusted WG members) have full, granular control of:
      - who can make edits at all
      - whether users can commit edits directly to the repo’s main branch, or some/all edits require creation of a PR
      - exactly which users are allowed (if anybody) to commit edits directly to the main branch without a PR, and which users must instead submit their edits as PRs (for review)

### Notable aspects of the implementation of this proposal

Here are few things worth noting about the implementation of https://github.com/w3c/csswg-wiki:

#### Site design
As noted in https://github.com/w3c/csswg-wiki#frontend-design, the https://github.com/w3c/csswg-wiki site is:

- implemented with a modern, accessible, responsive frontend built with vanilla HTML, CSS, and JavaScript
- follows WCAG 2.1 AA guidelines
- looks great on mobile phone screens, and has great UX even on mobile screens
- works well cross-browser

#### Search feature

As noted in https://github.com/w3c/csswg-wiki#search, the site provides a ([Lunr.js](https://lunrjs.com/)-based client-side) full-text search feature.

#### Markdown enhancements

As noted in https://github.com/w3c/csswg-wiki#conversion-process, the Markdown-to-HTML converter  supports:

- **Definition-list conversion to HTML `dl`/`dt`/`dd`**

   To produce `dl`/`dt`/`dd` output in HTML, the following markdown can be used in the source: 
   ```
   Term
   : Definition
   ```
   Existing wiki.csswg.org content uses definition lists extensively — so it’s important that the replacement also support them.

 - **GFM-style “alerts” (admonitions)**

   Admonitions can be represented in Markdown source using the same syntax supported in other GitHub content:

   ```
   > [!IMPORTANT]
   > Admonition content here
   ```






-- 
GitHub Notification of comment by sideshowbarker
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13504#issuecomment-3909108055 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 16 February 2026 15:32:25 UTC