Rework tracks grouping/presentation #1170
Open
+155
−42
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 cyf-curriculum canceled.
|
✅ Deploy Preview for cyf-common canceled.
|
✅ Deploy Preview for cyf-launch 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-tracks 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. |
5 tasks
✅ Deploy Preview for cyf-itd canceled.
|
|
Oh Daniel do you want to break my heart! Absolutely not! 😂 😭 I mean, I completely agree with the organisation and the descriptions, but we can't have this layout I will DIE. I think it might another case for Taxonomies? And we can put some kind of info dump underneath if we need to. |
As per our last syllabus team meeting, we think these are the three families of tracks we have. Explain a bit of context as to what each category is. This maybe makes more sense to do under the headings of each group of tracks? But then the text is going to be awfully skinny... Also, self-study tracks may have specific prereqs - we should list them so people know what they may want to opt to study.
Some things we should decide: * Do we want to still support menus, or should we just make everything be a taxonomy? * How do we want to handle compatibility here? I've renamed the map frontmatter to menus_to_map to make it more clear what it is, but this is a breaking change - I can add in a fallback for compatibility, or just have this be a break. If we're deleting the menus way and forcing taxonomies, we should almost certainly do that as a breaking change. If we're going to allow both, it's more of an open question. And we need to style the new layout, because it's hideous.
illicitonion
force-pushed
the
rework-tracks
branch
from
518c1a7
to
b2e1e29
Compare
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.
What does this change?
As per our last syllabus team meeting, we think these are the three families of tracks we have.
Explain a bit of context as to what each category is. This maybe makes more sense to do under the headings of each group of tracks? But then the text is going to be awfully skinny...
Also, self-study tracks may have specific prereqs - we should list them so people know what they may want to opt to study.
Common Theme?
Org Content?
Updates tracks metadata.