Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 1 min read

I built a GTA 6 fan wiki where every sentence needs a source

GTA VI came out on November 19, and within hours the web was full of "facts" about its lead character, Lucia Caminos. Some were official, some were rumors from the 2023 trailer era, and most pages didn't say which was wh

GTA VI came out on November 19, and within hours the web was full of "facts" about its lead character, Lucia Caminos. Some were official, some were rumors from the 2023 trailer era, and most pages didn't say which was which.

So I built luciacaminos.wiki, an unofficial fan reference with one hard rule: every claim cites a source, either Rockstar or a major outlet.

How it works

Static Next.js site (output: 'export'). Pages are Markdown files with frontmatter, so adding a fact means editing a text file.

Citations inline. After each claim I write [[source-id]]. A registry (sources.json) maps each id to the source's URL, outlet and date. Footnote numbers are assigned per page by first appearance.

A citation linter that fails the build. The content checks run inside next build, and they fail on uncited paragraphs, unknown source ids, bad dates and banned phrases. A content mistake breaks the deploy instead of going live.

Official images only. Rockstar screenshots, compressed under 350 KB, credited and cited like any other claim.

Faster Bing indexing with IndexNow. After updating a page I ping IndexNow so Bing re-crawls it.

What's on it

Lucia's official backstory, the actress, Lucia and Jason, the trailers, quotes and an FAQ, plus a clear line between what's confirmed and what isn't.

If you spot something wrong, tell me. A correction with a source is exactly what the site is built for.

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.