move site configuration from myst.yml to a separate site.yml file - #312
Merged
Conversation
✅ Deploy Preview for ucospo-net ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Collaborator
Author
|
pre-commit.ci autofix |
LauraLangdon
approved these changes
May 19, 2026
LauraLangdon
left a comment
LauraLangdon
left a comment
Contributor
There was a problem hiding this comment.
This seems good! I have some thoughts on maybe duplicating our sidebar links in the header so that can be ported over as well, but that's not in the scope here!
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
2 participants
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.
As discussed in #307, I am testing putting the Sustainability Playbook in a separate repo, and then configuring the playbook repo to inherit certain HTML assets (favicon, footer, etc.) from the core site. This workflow is based on the workflow used by the JupyterBook project, described here (https://jupyterbook.org/blog/posts/2026/multi-repo).
I'd be happy to explain why I think this is a better choice than sticking it on the main website, and happy to discuss. It's actually live right now at https://ucospo.net/playbook. (Obviously, this is an "unlisted" link; you can only find it if you type the URL in your browser.) I hope I did not overstep my bounds by creating it; we can delete it/take it down if you don't like it.
In order to test out the inheritance thing, I need to be able to point my repo's myst.yml file at just the site configuration data from your repo. Currently, that's located within the myst.yml file, but when I point my repo to your myst.yml file, I inherit everything, including your ToC--not good.
If we put ucospo.net's site config data into a separate site.yml file, and remove it from your myst.yml file, then I can point my configs to your site.yml file so that I inherit only a few assets, not absolutely everything. I made this split on a feature branch, deployed the site locally, and it worked. Your site looks exactly the same, and my site inherited your stuff. (Well, it couldn't find the images, but I think using absolute github URLs instead of local relative paths will fix that.)
This PR proposes to split the myst.yml file into two files: myst.yml and site.yml. With a separate site.yml file, I'll be able to proceed with sprucing up the playbook site.