-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Site data #48
Merged
Merged
Site data #48
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
✅ Deploy Preview for gracious-brattain-bdd606 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
I realized I had that last commit, c134673, on the Otherwise, it looks good, so merging! |
Merged
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 is a major restructuring of the main configuration file for the website and its source repositories. It was previously called
source-repos.js
, but has been renamed tosite-data.js
to reflect the broader scope, which now includes site metadata and caching details as well. The source repositories themselves are now flattened, and can specify a template or just use the default template that's being used for the docs. However, none of this should effect how those source repositories need to structure their ownmkdocs.yml
orconfig.yml
files internally.This work was preliminary to the work required to make the community blog possible, due to the need to use Front Matter, a separate template from the docs, and a different folder structure w/o necessarily using a
config.yml
file.I'll follow up with a separate PR for the blogging work, which should wait to be merged until there is some actual content we want to publish, but this PR can and probably should be merged as soon as its preview build has been tested fully on the Netlify.