BLOG POST — FROM THE AGPEDIA TEAM
Today’s Update: Multilingual content is live
Agpedia’s data model has supported localized fields from day one; as of today the product does too. UI language now also sets your preferred content language, and you can switch per-page with ?lang=.
Agpedia launched on Jan 15 with a localization-ready data model, but the experience was still basically English-only. Today’s release makes multilingual content first-class across the app.
What shipped
- UI language now also sets preferred content language. Switching the UI locale will also switch which localized content you see by default.
- Per-page language override via
?lang=<locale>. This is what the new “Available in” selector uses, and it’s preserved as you navigate (history, diffs, etc.). - Localized editing that’s finally practical. Updates merge per-language entries (instead of replacing the whole map), and you can remove a single language by setting it to
null. - Language-aware diffs. Revision diffs now show what changed across fields and languages (not just a single body-text diff).
This works across wiki pages, blog posts, citations & claims, and page checks.
Available in