Editing the wiki

Administrators maintain this wiki through a browser editor. Production editors need GitHub write access to the wiki repository. Open Admin to edit documentation, articles, and website settings.

What you can edit

• Docs · English, Docs · Français, and the other language collections contain each language’s document tree. Use the same path in every language, such as guides/configuration.
• Articles: publish dated posts and use the editor’s language controls to translate them alongside English. Keep the same slug.
• Plugin directory: translate overview pages and set documentation or purchase links.
• Website settings: edit homepage copy, menus, and quick links for each language. The site title, Discord, and GitHub links are shared.
• Media: upload images and insert them into Markdown.

Write a page

1. Choose the collection and language matching your topic.
2. Create an entry and fill in the title and short description.
3. Write in Markdown or use the rich-text editor. Use headings to divide longer pages.
4. Set the sidebar order to choose where a documentation page appears.
5. Save with the draft switch enabled while a page is unfinished.
6. Turn off the draft switch and publish when the page is ready.

The editor shows a content preview. It is not an exact preview of the full website. Publishing commits changes to GitHub. The current site uses manual Wrangler deployment, so a maintainer must build and deploy the new content before it becomes visible. Automatic deployment requires a separately configured workflow.

Missing translations show the published English page with a notice. Draft translations stay unpublished; their public route may still show the English fallback. The language selector keeps readers on the equivalent page.

Local editing

Run npm run dev and npm run cms in separate terminals. Open http://localhost:4321/admin/. The local editor writes files to the checkout; it does not push them to GitHub. Review changes in Git before committing.

Review before publishing

Check links, example commands, code fences, and image descriptions. Keep unfinished claims out of a published page. A hidden sidebar item is still publicly accessible; use Draft to remove a page from the public build and search.