Externalize data #34
Open
Externalize data #34
Conversation
This file contains 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
…e.js`, to be moved into an external JSON file
❌ Deploy Preview for spyder-website-preview failed.
|
…. Updated some packages
…slation support to the Blog, Download and About pages
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 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.jsloads data from the YAML source and exports variables accordingly. This preserves compatibility with the previous configuration.routes/content.yamlwill provide content for the front page,routes/about/content.yamlwill provide content for the/aboutroute, and so on. Only the/blogroute does not require an external content file.