Limitations
A published Wikven site is files: HTML, CSS, JavaScript and images, with nothing running behind them. Anything MediaWiki does by answering a request when a reader asks for it is therefore not part of the export. This page is the list, and what stands in for each where anything does.
What a live wiki does and an export does not
- All special pages, and the action API behind them
- All editors (WikiEditor, VisualEditor and CodeEditor); you edit the source files instead
- Accounts, and everything keyed to one: preferences, watchlists, notifications, user pages
- Page histories and diffs
- Discussion pages as a workflow, and recent-changes feeds
What stands in for them
- Editing and history
- Your repository. The "Edit", "View history" and "View source" links on each page lead to the page's source file there, wherever you host it; see the
WikvenEditUrlsetting and the two beside it. - Reading preferences
- A Settings page the build writes, carrying the reader's colour theme and, where a site builds more than one skin, which skin to read it in.
- Search
- Done in the browser. The build writes a search index alongside the pages and the search box queries that.
Special:Version- The Licenses page, where the build lists what it ran on and the extensions and skins the site publishes, with the licenses they declare.
Limits on what you write
Everything above is the reader's side: what a live wiki answers for and an export has no server to answer with. There are limits on your side too, and they are about names. A handful of directories in the output are the build's own, so a subpage named after one of them is written where something else already goes; and a page that carries translations claims every subpage of itself named for a language. Neither is refused and neither warns, so both are worth reading before you name a page: see Names a subpage cannot take.