-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
Externalize data to make the website translatable and add Spanish translation #34
Conversation
…e.js`, to be moved into an external JSON file
✅ Deploy Preview for spyder-website-preview ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
…. Updated some packages
…slation support to the Blog, Download and About pages
66b8a8d
to
312ea20
Compare
…s in the front page
…arnings on Chrome
…s (non-translatable strings and settings)
…ove formatting on some files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a fantastic improvement @conradolandia!! Thanks a lot for your work on it!
I left several suggestions for the Spanish translation, the rest looks good to me.
Co-authored-by: Carlos Cordoba <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All suggestions approved and ready to merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, thanks @conradolandia!
This PR aims to find and externalize all static data on the website so it can be imported from YAML files.
The website now loads its data from 4 sources, depending on the needed data:
$lib/config/content.yaml
. The file$lib/config/index.js
loads data from the YAML source and exports variables accordingly. This preserves compatibility with the previous configuration.routes/content.yaml
will provide content for the front page,routes/about/content.yaml
will provide content for the/about
route, and so on. Only the/blog
route does not require an external content file.Fixes #21
Fixes #8