You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we have a few high level keys in the myst.yml including project/site/version/extends. It is confusing to users where to put the keys (mostly always under project). Additionally, when writing a shared configuration, for example, abbreviations, authors, etc. that requires you to write it under the project key.
Instead, I suggest that we lean into the single project, and flatten all keys that are in the project. Moving from:
With the above change, site will have way fewer fields; this means we can remove the site.options key and just define those options directly on the site.
Thanks @fwkoch -- I am a big fan of these changes and think it would make the onboarding simpler, and the code a lot simpler to reason about. This also is closer to mimic-ing how the exports options work, which is helpful.
Right now we have a few high level keys in the
myst.yml
including project/site/version/extends. It is confusing to users where to put the keys (mostly always under project). Additionally, when writing a shared configuration, for example, abbreviations, authors, etc. that requires you to write it under the project key.Instead, I suggest that we lean into the single project, and flatten all keys that are in the project. Moving from:
to
There are still potentially some site options to configure, but they will be obviously related to the theme (nav links, footer, etc.).
@jmunroe
The text was updated successfully, but these errors were encountered: