Conversation
eelcoj
pushed a commit
to Rails-Designer/perron-site
that referenced
this pull request
Feb 5, 2026
Related branch/PR: Rails-Designer/perron#127
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
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.
This PR is to explore how to add i18n/locale to Perron. Since Perron is just Rails most of the i18n code can be used.
But how to structure the content files? Currently leaning towards
app/content/:collection_name/:locale/*/*.*(another option would beapp/content/:collection_name/*/*.:locale.md). The former logic is now added in this PR and could be shipped as-is.Tentative implementation then looks like:
Biggest unknown now is how to add these locale-based routes to the build step.
Closes: #128