Maintain this documentation
Author, organize, publish and retire articles through the existing website CMS.
Author in the existing CMS
Authorized staff open Website pages, create a page with a unique readable slug, and enable 'Developer documentation article'. Set title/description, category/subcategory, order, optional engine name and support status. Write rich article content in the supplied field and use the live article preview. No application source edit is needed for ordinary article changes.
Review and publication
Save the draft, review the exact version and publish using the existing CMS controls. content.edit and content.publish remain separate permissions; publication requires the established recent-authentication protections. Drafts do not appear in public search. Archive removes an article from the center and search; published direct URLs become unavailable. Restore or publish a revision through the same history workflow. Concurrent updates retain the existing revision conflict protections.
Content conventions
Use second/third-level headings for automatic anchors/TOC; fenced code with a language for highlighted copyable examples; pipe tables; lists; blockquote callouts; safe links and image syntax. Raw HTML never executes. Related articles are stored as page slugs. Attachment fields accept local paths or HTTPS file URLs; choose generated resources or a separately hosted file and verify retrieval before publishing. The documentation attachment uploader reuses existing media storage and permissions for ZIP/source/text/PDF files up to 20 MiB. Uploaded files are public immediately and are forced to download with a non-executable MIME type. Do not upload private material.
Technical maintenance
Build-time generation produces the SDK declarations from the real interface, the extension list from the package validator, lifecycle pages from the shared event-name constant and SHA-256 manifests from actual downloads. The public event inspector queries current published schemas instead of copying them into prose. Technical prose still needs review when behavior changes; no system can infer every game-specific rule from a schema alone. The additive documentation seed only inserts missing pages and preserves edits, drafts and archives. Regeneration does not overwrite CMS content. New or updated example archives require the source build/deploy workflow; new article categories and linked attachments do not require a redesign.