We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While we're not routinely tracking low-level Jekyll improvements at this point, occasionally something might catch my eye and this is one of them:
jekyll/jekyll#8167
Seems like something important to improve here as well.
The text was updated successfully, but these errors were encountered:
I'm all for additional i18n support. I'll take a look at the Jekyll PR and see if it could be simply dropped into Bridgetown.
I also don't think there's enough people using Bridgetown to worry about extreme-edge cases where URLs May change as mentioned in the Jekyll issue.
Sorry, something went wrong.
jaredcwhite
Successfully merging a pull request may close this issue.
While we're not routinely tracking low-level Jekyll improvements at this point, occasionally something might catch my eye and this is one of them:
jekyll/jekyll#8167
Seems like something important to improve here as well.
The text was updated successfully, but these errors were encountered: