Repository Maintenance — 2026-07-28 Weekly

Scheduled weekly check. Inspected all documents modified in the past 24 hours on z6Mko5npVz4Bx9Rf4vkRUf2swvb568SDbhLwStaha3HzgrLS (Seed Hypermedia public site).

High Priority

1. `/knowledge-bases` page missing from site navigation

Problem: The knowledge-bases page is a substantial, well-structured landing page about knowledge bases. It was updated today but is absent from the site's navigation bar, which only lists: Resources, Blog, Team, Support.

The homepage links to it via the "Create your knowledge base" button, but once a visitor navigates away, there is no way to return to this page from the nav.

Recommendation: Add /knowledge-bases to the site navigation. If the nav bar is getting crowded, consider grouping under a "Product" or "Features" dropdown.

2. Navigation label / path mismatch for Support/Community

Problem: The navigation bar displays the label "Support" but links to path /community. The page title metadata is also "Support". This creates confusion: the path says "community", the nav says "Support", and the actual content is a mix of community discussions and support topics.

Recommendation: Align the label, path, and title. Pick one identity:

If this is a Community page: rename nav label to "Community", keep path /community

If this is a Support page: rename to path /support, keep nav label "Support"

The content currently serves both purposes. Consider splitting into separate /support (bugs, UX, tutorials) and /community (discussions, related projects) pages if the distinction is meaningful.

Medium Priority

3. Content overlap: homepage vs `/knowledge-bases`

Problem: The Seed Hypermedia homepage was significantly expanded today (10+ rapid iterations). It now includes extensive sections about knowledge base use cases:

"Infrastructure for collective intelligence"

"Built for communities developing knowledge over time"

"Use cases" (Research communities, Open-source projects, Learning communities, Civic networks)

Meanwhile, knowledge-bases covers nearly identical ground with its own sections:

"What you can build with Seed" (Community knowledge bases, Research, Open project docs, Public knowledge communities)

"Why Seed is different"

"How it works"

The duplication is not harmful at this stage — the homepage is marketing-oriented and /knowledge-bases goes deeper. But as both pages evolve, they risk diverging in messaging.

Recommendation: Treat /knowledge-bases as the canonical feature page. The homepage should summarize and link to it rather than duplicating its content. Add a clear CTA on the homepage like "Learn more about knowledge bases →" pointing to the full page.

4. Homepage underwent 10+ rapid iterations in ~40 minutes

Problem: The homepage was edited 10+ times between 14:24 and 15:15 UTC today by Gabo (z6MkrbYsRzKb1VABdvhsDSAk6JK8fAszKsyHhcaZigYeWCou) and the Seed account. The page structure shifted dramatically: from a minimal shell (query block + download CTA) to a feature-rich landing page with 8+ major sections. While rapid iteration is normal during development, the intermediate versions are publicly visible.

Recommendation: Consider using drafts or a staging account for major homepage redesigns, then publish the final version. This keeps the public-facing page stable during iteration.

Low Priority

5. Very long community document path

Problem: The path /community/great-video-from-alan-kay-talking-about-agents-and-tools-in-1990 is 71 characters. While descriptive, such long paths are unwieldy to share and type.

Recommendation: Consider a shorter path like /community/alan-kay-agents-and-tools-1990. Use the current long form as the document title instead.

6. No Librarian repository documents modified this week

Observation: No documents in the Librarian's own account (z6MktvJHDTxvWXVCnrPvQqrD6ZN3b2tQG7ZQua6epbEUTb3y) were modified since the last report. The maintenance hub and weekly report structure continue to function well.

Positive Observations

The /knowledge-bases page has excellent structure: clear headings, logical flow (problem → solution → use cases → differentiation → how it works), and a strong closing CTA. It serves as a good model for feature landing pages.

The Resources page is well-maintained with 9 linked guides covering setup, publishing, design, and collaboration.

No orphan documents were detected in the recently modified set.

No duplicate pages were found.

The navigation structure (Resources, Blog, Team, Support) is clean and scannable, even if it needs the /knowledge-bases addition noted above.