Website IA overhaul: Migration Tracking

[bumbleblue]

Used Claude Sonnet 4.6 to (re)generate a plan for migration on the Hugo branch. This follows the work from @bumbleblue @juliarodesign (and with input from @jdittrich and @Erioldoesdesign ) on the content front. Content edits are being made in our shared Nextcloud. This issue is to track the code migration on the branch for visibility and for reference. Pinging @AnXh3L0 and @SaptakS for a sanity check.

This tracks all work for the information architecture redesign on the feat/hugo-monorepo-ia-overhaul branch. Everything merges to master in one go at the end.

Full details for any task: docs/migration-plan-hugo.md · Content brief: docs/content-needed.md · Test plan: docs/test-plan.md

[dev] = code/config · [content] = writing · [design] = design work needed

---

Phase 0 — Prep

• 0.2 Delete content/goals/ directory (URL conflict with goals.md) [dev]
• 0.3 Delete content/archive/, add /summit/ redirects to events [dev]
• 0.4 Clean up undated/duplicate files in content/articles/ [dev]
• 0.5 Remove Twitter links; fix Mastodon URL to fosstodon.org [dev]
• 0.6 Verify no front matter errors in content/jobs/ [dev]

Phase 1 — Structure & redirects

▎ Hugo uses aliases: in front matter for redirects (built-in, no plugin). Old source files must be deleted in the same commit as the new file.

• 1.1 Create content/about-us/_index.md; delete goals.md, faq.md [dev]
• 1.2 Move manifesto.md → content/about-us/manifesto.md [dev]
• 1.3 Move code-of-conduct.md → content/about-us/code-of-conduct.md; fix Twitter refs [dev]
• 1.4 Move governance.md → content/about-us/governance.md; delete processes.md [dev]
• 1.5 Move by-laws.md → content/about-us/by-laws.md [dev]
• 1.6 Create content/about-us/how-to-join.md; delete contribute.md, people/join.md [dev]
• 1.7 Create content/forum.md (placeholder) [dev]
• 1.8 Create content/imprint.md (placeholder) [dev]
• 1.9 Add aliases: ["/articles/"] to content/resources.md [dev]
• 1.10 Verify: hugo build clean, all new URLs return 200, all old URLs redirect [dev]

Phase 2 — Navigation & footer

• 2.1 Update hugo.toml nav: remove Goals/Articles/Archive, add About Us, point Forum to /forum/ [dev]
• 2.2 Update data/social.yaml, data/quicklinks.yaml, layouts/partials/footer.html — remove stale links, add Imprint [dev]

Phase 3 — Content

• 3.1 Write /about-us/ — merge goals + FAQ into prose, add TOC [content]
• 3.2 Write /about-us/how-to-join/ — adapt contribute.md + issue Suggestion: Restructure Website: Create a page on joining the Open Source Design org #506 [content]
• 3.3 Write /forum/ — short description + link to Discourse [content]
• 3.4 Write /imprint/ — fiscal info, Open Collective as sponsor [content]
• 3.5 Convert resources.md → section (_index.md); restructure with lead article (Suggestion: Restructure Website: Create Page on being a designer in open source software #505) + curated list [content] [dev]
• 3.6 Move 12 event write-ups from content/articles/ → content/events/; add aliases for old URLs [dev]
• 3.7 Move 6 resource posts from content/articles/ → content/resources/; add aliases [dev]
• 3.8 Delete remaining articles (classified "remove"); delete content/articles/ dir + layout [dev]
• 3.9 Delete entire content/people/ collection + layouts/people/ templates [dev]
• Backlog Port FOSDEM 2026 wrap-up from master → content/events/ with adapted front matter [dev]

Phase 4 — Design & layout

• 4.1 Redesign events listing: ticker style, write-ups visually distinct, feeds homepage [design] [dev]
• 4.2 Homepage redesign: hero, sections, events sidebar, jobs section, remove Articles + Conferences + Contact sections [design] [dev] [content]
• 4.3 Footer template cleanup: remove dead code after 0.5 + 2.2 [dev]

Phase 5 — Validation & launch

• 5.1 Run link checker (hugo build && npx broken-link-checker http://localhost:1313) [dev]
• 5.2 Final review checklist (see migration plan) [dev]
• 5.3 Archive docs/sitemap-current.md, update to reflect live state [dev]
• 5.4 Merge feat/hugo-monorepo-ia-overhaul → master [dev]

---

Before starting Phase 1: confirm hugo server builds cleanly on the branch and you have write access.
Before Tasks 3.6/3.7: confirm the URL pattern Hugo generates for content/articles/ by checking a live article URL — needed to write correct aliases.

[jdittrich]

@bumbleblue @juliarodesign The suggested structure in "about us" and "resources" needs subpages. Did you already have some ideas how users would get there? Two ways that come into mind would be

1. Have (pop-up) submenus
2. Have pages that branch out to subpages via cards or some other form of semi-structured links (i.e. not links in the text via linkified words but some other way to collect and highlight them)

If we go with 2) we spare us from implementing interactive and often finnicky menus but needs some content on the main pages before branching in the subpages.