Merged
Conversation
…tilingual pipeline - split site config into language-specific files (_quarto-en.yml, _quarto-ja.yml) and add language-specific metadata files (_metadata-en.yml, _metadata-ja.yml) - remove legacy _metadata.yml and keep _quarto.yml focused on shared/base settings - migrate logo assets to locale-specific variants (en/ja, light/dark) and update references across Quarto, metadata, and shared theme.scss - keep a shared theme.scss and handle language-specific behavior via html[lang="en"|"ja"] selectors (fonts + logo mapping) - ignore generated language build outputs in .gitignore (.site-*) - update logo source SVG export labels/paths for new naming - normalize regenerated hypergroove master sources for rhythmpress/CMS compatibility
- rename index-en.qmd to en/index.qmd - rename index.qmd to ja/index.qmd - align homepage source layout with language-scoped content structure
After moving root index pages into en/index.qmd and ja/index.qmd, Quarto started emitting two warning classes during render: 1) Invalid lang values like ../en, ../../en, ../../../en 2) Unresolved links targeting index.qmd Root causes: - lang: en / lang: ja collided with directory names (en, ja) in path-aware metadata resolution, producing path-like lang values. - Navbar/sidebar metadata still referenced index.qmd even though the files were relocated to en/index.qmd and ja/index.qmd. - CSS language selectors were exact-match (html[lang="en"], html[lang="ja"]) and needed to support region-tag variants. Changes made: - _quarto-en.yml: set lang: en-US; updated render/navbar/sidebar references from index.qmd to en/index.qmd. - _quarto-ja.yml: set lang: ja-JP; updated render/navbar references from index.qmd to ja/index.qmd. - _metadata-en.yml: updated navbar href from index.qmd to en/index.qmd. - _metadata-ja.yml: updated navbar href from index.qmd to ja/index.qmd. - .assets/websites/theme.scss: changed language selectors to html[lang|="en"] / html[lang|="ja"] for en-US / ja-JP compatibility while keeping language-specific font/logo behavior. - en/index.qmd and ja/index.qmd: set rhythmpress conf path to ../_rhythmpress.conf for the relocated directory layout. Result: - Rendered pages now use valid lang tags (en-US, ja-JP). - No path-like lang warnings. - No unresolved index.qmd warnings from relocated entry pages. - Local /en/ and /ja/ routes work when previewing from .site.
…le configs Add language-switcher runtime assets and root entry page wiring so the navbar can host a language switcher and load the generated module across the site.\n\nUpdate _quarto.yml to include the switcher slot in navbar config and to load /lang-switcher.generated.mjs in the shared header includes. Add index.qmd as the runtime root entry page and add generated switcher modules used by the site runtime.\n\nStop tracking generated locale-specific Quarto config files (_quarto-en.yml and _quarto-ja.yml) and add _quarto-*.yml to .gitignore so regenerated files do not create repository drift.
Replace the legacy two-step CI build flow (rhythmpress build + quarto render) with the new unified rhythmpress run-all command. This aligns deploy.yml with the current Rhythmpress orchestration model where run-all executes: - rhythmpress build - rhythmpress render-all - rhythmpress assemble Why this change: - render-all renders each language profile from _quarto-*.yml into .site-<lang> outputs. - assemble merges those profile outputs into the final .site tree used for publication. - This avoids drift between local and CI build wiring and keeps the pipeline behavior consistent with multilingual project configuration. Also install rsync in the workflow system dependencies because assemble relies on rsync to merge site directories. publish_dir remains ./.site, which is still the correct GitHub Pages publish target after assemble.
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
1 participant
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.
No description provided.