A small game wiki can become difficult to maintain when its navigation, sitemap and article files are edited separately. For Underkeep Wiki, we use one content inventory to drive the generated site.
The content model
Each guide has a slug, publication status, title, summary, update date, source list, and Markdown body. The generator uses published entries to create HTML routes and links, while draft entries stay out of the site. This makes publication an explicit content decision instead of a matter of remembering several manual edits.
Validate before replacing output
The build checks configuration, references and internal links. Invalid input should fail the build rather than quietly producing a broken navigation link or an incomplete sitemap. In this project the generated sitemap and canonical URLs use the production domain.
Keep game-specific data out of the renderer
The rendering code handles generic concepts such as cards, article figures, source lists and categories. The content package supplies the Underkeep descriptions, images and links. This keeps the site independent from the original template and lets updates remain localized.
Make claims easy to check
Platform information links to official store and developer sources; player build suggestions are identified as player advice. The party-building page is one example. Exact maps and secret coordinates are not included until there is enough evidence to verify them.
Before shipping, build the site, inspect desktop and mobile layouts, follow important links and request the live sitemap. A successful build confirms the generated files are internally consistent; it does not guarantee search-engine indexing.
This article was prepared with AI assistance and reviewed against the project configuration and build checks.
Top comments (0)