Your documentation is still in your Mum’s filing cabinet
Your documentation is still in your Mum’s filing cabinet It’s kind of wild when you stop and think about it. Most documentation is arranged into files, folders and hierarchies. A document goes inside a folder inside another folder and on the surface it’s well tidy.
- ▪Your documentation is still in your Mum’s filing cabinet It’s kind of wild when you stop and think about it.
- ▪Most documentation is arranged into files, folders and hierarchies.
- ▪A document goes inside a folder inside another folder and on the surface it’s well tidy.
Sidebar.io files mainly under design. We currently carry 33 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Gerireid |
| Canonical URL | https://gerireid.com/blog/organising-documentation-for-humans-and-ai/ |
| Publication time | Fri, 26 Jun 2026 08:02:36 GMT |
| Retrieval time | 2026-06-26T08:07:31.019Z |
| Last seen | 2026-06-26T08:07:31.019Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Jitv04WNuqbM |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Your documentation is still in your Mum’s filing cabinet It’s kind of wild when you stop and think about it. Most documentation is arranged into files, folders and hierarchies. A document goes inside a folder inside another folder and on the surface it’s well tidy. The trouble is that knowledge rarely behaves that way. A component accessibility decision can affect design, engineering, content and customer support. So where do you put the documentation for it? The more complex the subject, the more awkward that choice becomes. The modern desktop was developed at Xerox PARC in the 1970s. Early graphical user interfaces borrowed heavily from physical office concepts like documents, folders and filing systems because they were familiar to office workers.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Gerireid.
Discussion
0 commentsMore from Gerireid
