Consider grouping workbooks by topic rather than style of work

[illicitonion]

Currently the workbooks are presented as "here's a bunch of reading", "Here are a bunch of projects", and such.

Instead grouping by theme: "Here is some reading around processes, and some projects around processes", ideally also with concrete learning objectives of the reading, would help to split up and plan work better.

[SaadiaELF]

I would also consider the following point when possible :

• the general goal of the sprint (giving context)
• the order of the theme/modules

[SallyMcGrath]

on this, as I'm writing the new metadata driven pages (in pieces between calls)

it looks like you want things grouped by theme.

In the new backlog workbook view, you will have ticket type expandable blocks. These will have learning objectives if they pull from primers and projects and the themes as tags/labels.

Q: Do you still want them grouped by theme, or just in the order of blocks listed in the front matter?

The question is about the order the items are shown on this view. At the moment, they are shown in the order they are listed. Do you want them to be grouped by theme, which requires me to reorder this sequence? Or will you expect them to show in the order you list them and you may group by theme manually if you choose?

[SallyMcGrath]

Also, I've written a featured link block, where the src is just any external link, which I will put in anyway for the main curriculum, but actually maybe these links should be local blocks so they can carry more metadata? Make sense? EG instead of

+++
[[blocks]]
name="Ops School Shell 101"
src="https://www.opsschool.org/shell_tools_101.html"
caption="Get familiar with shell tools"
time=120
+++

it would be

+++
[[blocks]]
name="Ops School Shell 101"
src="systems/shell-101
+++

going to

+++
title="Ops School Shell 101"
time=120
[objectives]
1="Examine processes running on your system"
2="Send a signal to a running process using `kill`
themes=['linux proficiency', 'how computers work']
+++

Your link and preamble here.

---

[illicitonion]

Q: Do you still want them grouped by theme, or just in the order of blocks listed in the front matter?

The question is about the order the items are shown on this view. At the moment, they are shown in the order they are listed. Do you want them to be grouped by theme, which requires me to reorder this sequence? Or will you expect them to show in the order you list them and you may group by theme manually if you choose?

I'm not sure tbh! I think either could be sufficient/interesting. If we are grouping by theme, we'd probably also want to order the themes somehow (more things to configure, sigh), but ordering in block-order and displaying the themes as chips seems totally reasonable. The fact that some of your examples ^^ have multiple themes (which makes complete sense) maybe suggests towards just block ordering (unless we group by first theme or something).

I think my tl;dr is: Let's just order by block-order and display themes for now? If we wanted to add grouping by theme in the future, I think it wouldn't be too tricky (I could probably even do it myself without needing help!)

---

On in-line vs external blocks for links - I think either works. Currently we re-use the Troubleshooting Primer link in multiple sprints (though maybe with different learning objectives in each sprint), so external may be useful for deduplicating? But again, I think either works and changing our mind in the future is cheap.