Before you start
What problem are you trying to solve?
Current source comments and documentation still use “chrome” as an umbrella term for UI surrounding a page. The project has settled on page controls / page settings for the public vocabulary and rejected a chrome configuration object. Keeping the old term creates an unnecessary second concept and makes the documentation less precise.
Proposed solution
Remove the current use of “chrome” from source code, comments, tests, and documentation.
Use the specific term that describes the subject instead:
- “page controls” or “page settings” for per-page frontmatter behavior;
- “layout”, “shell”, “header”, “navigation”, “aside”, or the named component for rendered structure.
Update translated documentation alongside its source page. Do not change behavior, public configuration names, or historical GitHub issues.
Proper names and external identifiers, such as Chromium or chrome-launcher, remain unchanged.
Alternatives considered
Leave the old wording in internal comments while documenting the new vocabulary. This preserves two terms for the same idea and reintroduces the ambiguity the page-controls decision removed.
Additional context
Related: #15 settled the page-control vocabulary and explicitly rejected chrome as a public API term. This is a terminology cleanup, not a feature change.
Refined scope
“Browser chrome” may remain only where it literally means the surrounding UI of a simulated browser, including DuxtLiveWindow.chrome. Every other use of “chrome” must be replaced with the specific concept it describes.
Before you start
What problem are you trying to solve?
Current source comments and documentation still use “chrome” as an umbrella term for UI surrounding a page. The project has settled on page controls / page settings for the public vocabulary and rejected a
chromeconfiguration object. Keeping the old term creates an unnecessary second concept and makes the documentation less precise.Proposed solution
Remove the current use of “chrome” from source code, comments, tests, and documentation.
Use the specific term that describes the subject instead:
Update translated documentation alongside its source page. Do not change behavior, public configuration names, or historical GitHub issues.
Proper names and external identifiers, such as Chromium or
chrome-launcher, remain unchanged.Alternatives considered
Leave the old wording in internal comments while documenting the new vocabulary. This preserves two terms for the same idea and reintroduces the ambiguity the page-controls decision removed.
Additional context
Related: #15 settled the page-control vocabulary and explicitly rejected
chromeas a public API term. This is a terminology cleanup, not a feature change.Refined scope
“Browser chrome” may remain only where it literally means the surrounding UI of a simulated browser, including
DuxtLiveWindow.chrome. Every other use of “chrome” must be replaced with the specific concept it describes.