Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Decide whether Arch's editable defaults follow the page language

Open
#191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript

Research direction

Start with the header and news-grid widget files, then inspect the Arch locales and settingDefault in packages/render-engine/src/renderEngine.js. Compare the existing defaultKey settings with literal defaults and template fallbacks, and check how preview and export resolve them. Done means implementing the chosen scope so the selected defaults follow the page language in both preview and export, or updating LANG-034 and LANG-044 to clarify the decision.

Written by the indexing model from the issue text.

Description

question

Arch's editable starting texts ("Skip to main content", "Menu", "Read more", "View all", headings like "Latest News") stay English on translated pages until the owner edits them. Decide: translate them per language (proposed first for the header and "Read more"/"View all"), or leave them as the owner's to change.


Arch text settings start from literal English defaults and template fallbacks (| default: '…'), so an untouched translated page shows English: header skip link "Skip to main content", "Primary", "Menu", "Close menu"; News/Projects/Services Grid "Read more" / "View project" / "View service" / "View all"; widget headings ("Latest News", …); fallbacks such as "Learn More", "Download", "Before"/"After", "Play video", "Features". Settings with defaultKey (Core Form, services_grid.empty, …) already follow the page language, and every non-editable theme and core word is translated (Arch site.* 59/59 in el, core 15/15). Seen in the 2026-10-18 #115 review (LANG-034; LANG-044 makes the same claim). Options: (A) give Arch's editable defaults defaultKeys with locale entries in every language Arch ships; (B) only the always-present chrome (skip link, nav label, menu title/close, "Read more", "View all"), leaving headings; (C) leave it and reword LANG-034 to mean non-editable words only. Proposed: B now, A over time.

Done when: The chosen set resolves per page language in preview and export (new Arch version under updates/<version>/), or LANG-034 and LANG-044 say defaults are the owner's to translate.

Start: header widget, news-grid, Arch locales, settingDefault in renderEngine.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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tsiger/widgetizer

All issues in tsiger/widgetizer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.