Include links to original sources in success pages#1730
Conversation
✅ Deploy Preview for cyf-launch ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-common ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-sdc ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-programming ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-curriculum ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-tracks ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-itd ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-piscine ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This:
* Makes it easier to see what things are self-study vs have expected
evidence from backlog.
* Makes it easier to link back to where the topics were introduced.
The way we go about this is:
1. When fetching remote learning objectives, parse out to accumulate the
list of LOs, rather than just grabbing the whole markdown block
2. Pass LOs through a `{{<objectives>}}` shortcode, rather than just
pulling the shortcode in through the raw markdown.
3. Pass links to the original blocks into the rendering block.
4. Send both local and remote learning objectives through the same
rendering block (`common-theme/layouts/partials/objectives/for-success.html`)
which now includes links back.
illicitonion
force-pushed
the
success-page-links
branch
from
8f2897c to
11e16e9
Compare
github-project-automation
bot
moved this from 📋 Backlog
to 👀 In review
in Curriculum Planning
|
A follow-up thought that occurred while editing backlogs: these success criteria are capturing optional items too, eg. |
Yeah it's an interesting one. It does have Stretch in its title - maybe that's enough? Or maybe we want to group the stretch things after a "Stretch" heading? Implenetation-wise, though, I'm tempted to literally just grep the title for "Stretch", I don't think we currently want to build any more complex prioritising logic into the curriculum. |
|
Am I the only one that ticked all the boxes to see if there was a done effect (not disappointed) ? Although it is not immediately obvious that they are interactive tick marks. |
Yeah, it's more of an easter egg than a key feature (though we do generally demonstrate this when showing off the curriculum to people for the first time)
This is our "button" style, rather than our "link" style. I've re-styled them as links rather than buttons, WDYT? |
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in Curriculum Planning
3 participants
This:
The way we go about this is:
{{<objectives>}}shortcode, rather than just pulling the shortcode in through the raw markdown.common-theme/layouts/partials/objectives/for-success.html) which now includes links back.