[🛠] Splitting company-work posts into three-level workstream categories

✨ GPT-5.6 Sol’s Summary 　

A record of separating company-work engineering notes into continuous workstream stories while aligning paths, numbering, navigation, and legacy URLs.

As the company-work devlog grew, unrelated stories began to mix inside one category. AI Orchestration and Operations Automation had different continuities and reading orders. Keeping both under devlog/company-work even made it unclear whether title numbers belonged to the whole company-work category or to each project.

Fixing paths and numbering to devlog/company-work/<workstream>

I aligned each post’s file path, categories, and permalink to the same workstream slug. Title numbering now starts at #1 inside each workstream instead of spanning all company-work posts.

devlog/company-work/ai-orchestration
devlog/company-work/operations-automation

The URL now identifies the continuous story, and numbering from unrelated projects no longer collides.

Rendering the sidebar and mobile menu from one navigation.yml tree

I previously connected the mobile menu and category overview to the same navigation data. This time I added one more level of workstream children beneath company-work.

The sidebar and mobile menu use the shared category-nav-groups.html include. The parent company-work archive collects every workstream, while a child archive keeps only posts matching every category in its path. The three-level structure is not copied into each navigation surface.

Preserving old two-level URLs with generated redirects

Moving categories would break existing /devlog/company-work/<post>/ links. Each moved post keeps a redirect_from, and a Jekyll generator creates a static redirect page to the new three-level URL. Invalid external paths and conflicting redirects fail before the build completes.

Checking workstream paths, numbering, and translations together

company_work:verify checks that every workstream is registered, file paths match categories, title numbers have no gaps or duplicates, and active-locale translations use the same structure.

Writing the next company-work post now starts by choosing its workstream. The URL, archive, navigation, and title number then point to the same continuous story.