-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Ensure every site configures markup #1274
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for cyf-curriculum canceled.
|
✅ Deploy Preview for cyf-common ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-sdc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-programming ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-launch ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-tracks ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This avoids needing to notice and play whack-a-mole when things aren't configured as we expect. Also, add a --fix mode which will try to fix things for you.
✅ Deploy Preview for cyf-itd ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
0ed8841
to
4073615
Compare
✅ Deploy Preview for cyf-piscine ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-piscine ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Thank you for this. I do want this - but before we require it, can we check what can be inherited?
I'm not sure we do need to copy pasta as much config as we currently do, so would like to not bake that in (except the necessary). Can you read over this and have a think?
https://gohugo.io/getting-started/configuration/#configure-page
@@ -63,20 +63,24 @@ maxAge="6h" | |||
getenv = ["^HUGO_CURRICULUM_GITHUB_BEARER_TOKEN$"] | |||
|
|||
|
|||
theme = "common-theme" |
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.
I actually don't think we need to declare common theme any more if we're importing the module btw
@@ -24,17 +24,22 @@ baseURL = "https://sdc.codeyourfuture.io/" | |||
[params] | |||
googleFonts="https://fonts.googleapis.com/css2?family=Space+Grotesk:wght@300;500;700&family=Inter:wght@400;600&display=swap" | |||
|
|||
#this makes the section nav go the right way | |||
# because of this 'unexpected behaviour' https://gohugo.io/methods/page/nextinsection/ |
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.
Can this one not be inherited from theme?
Actually maybe this should be tidied up a bit more. What can we inherit from org-cyf-theme module?
https://gohugo.io/getting-started/configuration/#configure-page
This avoids needing to notice and play whack-a-mole when things aren't
configured as we expect.
Also, add a --fix mode which will try to fix things for you.