Hide language-only settings on single-language sites
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- developer-experience, frontend
Research direction
Start with the header schema, SettingsPanel.jsx, and validate-theme.js named in the issue; trace how settings are rendered and validated, then review the existing language-switcher tests. The change spans editor behavior, Arch schemas in the base and versioned paths, documentation, the theme skill reference, and catalog generation. Done when flagged rows hide on single-language sites and appear after a second language is added, with editor tests and the listed docs and catalog updates.
Written by the indexing model from the issue text.
Description
The header's language switcher settings show on single-language sites, where they do nothing. Let themes mark settings as "only with several languages" so the editor hides them.
Arch's header shows "Languages", "Show language switcher" and "Language switcher name" (languages_header, show_language_switcher, language_switcher_label) even when the site has one language, where they do nothing. Schemas have no conditional-visibility property and the platform doesn't know these ids (only Arch and archLanguageSwitcher.test.js reference them). Proposed design: a generic setting property "multilingualOnly": true the editor honours by hiding the row when useIsMultilang() is false; Arch flags its three rows (base and updates/<version>/). It is a theme-contract addition: document it with the setting types, add it to the theme skill reference and regenerate the catalog (scripts/build-theme-skill-contract.js), and let validate-theme.js accept it. Seen 2026-10-18 (#115 review, LANG-074).
Done when: Flagged settings are hidden on single-language sites and shown once a second language is added, with editor tests, docs and the skill catalog updated.
Start: header schema, SettingsPanel.jsx, validate-theme.js.
- Dominant language
- JavaScript
- Stars
- 162
- Forks
- 6
- Avg merge
- 12h 55m
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tsiger/widgetizer
-
question
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
tsiger/widgetizer#194 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tsiger/widgetizer#181 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
tsiger/widgetizer#175 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tsiger/widgetizer#174 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tsiger/widgetizer#173 ·
All issues in tsiger/widgetizer
Similar issues
-
enhancement p2 setup
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Query Log shows "Upstream" for CNAME cloaking, schedule, NXDOMAIN hijack and response IP blocksOpenbug good first issue query-log web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ferrous-networking/ferrous-dns#326 ·
Maintainers usually reply within 1 day
-
type: typos
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 4 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Ylianst/MeshCentral#8294 ·
Maintainers usually reply within 1 day