docs(contributing): document i18n locale field rendering types

[hanthor]

Summary

Translators have no way to know which locale keys support Markdown, which accept raw HTML, and which are plain text only. Using the wrong markup produces literal asterisks or tags in the rendered page.

Adds a Locale field rendering subsection under the i18n instructions in CONTRIBUTING.md with three tables:

• 24 Markdown fields (rendered via marked.parse())
• 2 raw HTML fields (Bazaar.Description, Bazaar.Additional — rendered via v-html)
• Plain text note for all remaining keys

Closes #648

Test plan

• CONTRIBUTING.md renders correctly in GitHub preview
• Verify tables match current component source (spot-check SceneUsers.vue, SectionBazaar.vue, SectionFooter.vue)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@castrojo, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 54 minutes and 34 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 01a2dbaf-d8d9-4958-8444-ff9f883bccd1

📥 Commits

Reviewing files that changed from the base of the PR and between e327e0d and 476181f.

📒 Files selected for processing (1)

• CONTRIBUTING.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/i18n-field-rendering-648

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[hanthor]

Code Review

Changes: 2 files (+48 lines). CONTRIBUTING.md (+42) and vite.config.ts (+6).

CONTRIBUTING.md — i18n rendering docs ✅

• ✅ Comprehensive field-type reference with 24 Markdown fields, 2 HTML fields, and plain-text default
• ✅ Clear component attribution for each field
• ✅ Practical guidance — translators can now avoid broken markup
• ✅ Well-positioned after the "Adding a new language" section

vite.config.ts ⚠️

• The coverage thresholds change is identical to PR #655 (closes #651). If #655 merges first, this will cause a trivial merge conflict. If this merges first, #655 becomes redundant. Either merge order works — just ensure only one lands.

Verdict

The CONTRIBUTING.md changes are correct and well-structured. The vite.config.ts overlap with #655 is minor and will self-resolve on merge. LGTM.

[hanthor]

Reviewed — clear docs on i18n locale field rendering types (markdown vs plain HTML). Closes #648. LGTM.

[castrojo]

The locale field rendering type documentation is exactly the kind of contributor guidance that belongs in CONTRIBUTING.md. Merging.

The merge-base changed after approval.

[castrojo]

Re-approving after rebase on main. The locale field rendering type docs are valuable for translators. All checks pass.

[castrojo]

LGTM - approving again to clear stale review state. The i18n locale rendering docs are good.

[castrojo]

Rebased cleanly onto main. LGTM - the locale field rendering documentation is valuable for translators.