docs(dnn): #457 Phase 1 — content audit + UI-strings CSV - #461
Merged
Conversation
…raction Epic #457 Phase 1 (Content Extraction), repo-side slice. Pure prep — no release artifact, no DNN write, release gate untouched. Key finding: the DNN export in this repo holds 2sxc/Razor TEMPLATES and static HTML, but NOT the portal content DB. Resource-dictionary values and all 2sxc content items (glossary, FAQ, homepage, per-rule content, page SEO/nav) are DB-only — they require a DNN/2sxc data export (jsboige access, Phase 4 dependency) before CSV-driven translation can run. This corrects the epic's optimistic in-repo estimates. Deliverables: - docs/dnn-localization/PHASE1-content-audit.md — full inventory: in-repo vs DB-only, per-source counts, static-page assessment, next steps. - docs/dnn-localization/dnn-ui-strings.csv — DatasetUpdater-compatible (key/context/source_file/fr/en/ru/pt/es/ar/fa/zh/notes). 2 hardcoded UI strings (real FR) + 8 @Resources keys (FR inferred, flagged verify-vs-DB). Also logs an i18n bug: _FallacyExplorer_Root.cshtml pins text_en/desc_en/ link_en + literal "find out more" regardless of culture (fix deferred to Phase 2/4, flagged to ai-01). Refs #457 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
clusterManager-Myia
left a comment
clusterManager-Myia
left a comment
Collaborator
There was a problem hiding this comment.
[NanoClaw]
Clean audit deliverable. No issues to block.
What this PR adds:
docs/dnn-localization/PHASE1-content-audit.md(160 lines) — inventory of translatable content across the Argumentum DNN site, split into repo-extractable vs DB-only buckets.docs/dnn-localization/dnn-ui-strings.csv(11 rows, header + 10 strings) — DatasetUpdater-compatible CSV with 2 hardcoded UI strings (real FR values) and 8 resource keys (FR inferred, flagged INFERRED).
Checked:
- All 4 referenced
.cshtmltemplates exist at the stated paths in the repo. - CSV columns match the described DatasetUpdater schema (
key, context, source_file, fr, en, ru, pt, es, ar, fa, zh, notes). - INFERRED values clearly flagged in both audit and notes column. The audit correctly distinguishes hardcoded strings (verifiable) from resource keys (DB-only, unverified).
- i18n bug on
_FallacyExplorer_Root.cshtml(hardcodedtext_en/desc_en/link_enregardless of culture) is documented with a reference to the exact template and line. Logged as a future fix item, not addressed here — correct scope for Phase 1. - Static HTML pages (
fallacies.html81KB,MariagePourTous.html38KB) are inventoried but wisely deferred — dumping raw HTML into a translation CSV without confirming live-nav status would be noise. - No secrets, no executable code, no risk to the release gate (explicitly untouched per the PR description).
Minor observation (non-blocking): The ui.rules.players_range FR value uses à HTML entity in the source template but the CSV stores the literal à. This is correct behavior for a translation-ready CSV (entities should be resolved before sending to translators), but worth noting for the Phase 2 implementer who will reference the CSV against source files.
Verdict: LGTM — accurate inventory, proper scope, well-structured CSV, clearly communicates blockers (DB-only content).
jsboige
added a commit
that referenced
this pull request
Jun 17, 2026
…tractor) (#525) Closes the "inventory content-types" idle task (ai-01 msg-…141408). Extends PHASE1-content-audit.md (#461) with a complete localization scope map and feeds the extractor (PR #524, merged). 5 content-types mapped (Argumentum-app scope only; DNN framework out-of-scope): - A custom-template hardcoded UI strings (2 keys) — extractor-done - B @Resources.* keys (8, values DB-only) — extractor-done (keys + DB-only flag) - C 2 static HTML content pages (fallacies.html ~24K chars + MariagePourTous ~13K, standalone FR prose, NOT CSV-driven) — repo-extractable gap, recommend separate document-tier translation lane (not the ui.*/res.* string task) - D 2sxc content items (glossary/FAQ/homepage/App resource VALUES) — DB-only, the bulk - E DNN page settings — DB-only. Both D+E need portal export (jsboige, gated). Findings: 26 2sxc apps installed but only Argumentum is custom (25 stock). The live « Materiel » coquille is NOT in any repo template (negative grep across Argumentum scope) → it's DB-only (content-type D), consistent with the "canonical FR lives in SQL" pattern. No prod mutation, no DB/RDP, no dnn-ui-strings.csv touch. Pure scope-map doc. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Epic #457 Phase 1 (Content Extraction), repo-side slice.
Key finding: DNN export holds templates/HTML but NOT portal content DB. Glossary, FAQ, rules per-page, SEO/nav = DB-only → requires DNN/2sxc data export (jsboige access) before translation can run.
Deliverables:
docs/dnn-localization/PHASE1-content-audit.md— full inventory (in-repo vs DB-only)docs/dnn-localization/dnn-ui-strings.csv— 10 UI strings, DatasetUpdater-readyAlso logs i18n bug:
_FallacyExplorer_Root.cshtmlhardcodes text_en regardless of culture.Patch by po-2023, applied by ai-01.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com