Skip to main content

[TEST] Behind the Wiki: How This Documentation Site Is Organized

· 2 min read
DeskPi Team
DeskPi Team
DeskPi engineers and product maintainers

🧪 This is a TEST article. It only demonstrates how a short, human-authored post looks on the blog list. Please delete the file blog/2026-09-13-behind-the-wiki.md after testing.

A quick meta note for the curious: this wiki is organized around one question — you have a board, what fits it? Everything else hangs off that.

The four shelves of the wiki​

  • Product pages — one page per case, rack and accessory, each with specifications, package lists and assembly steps.
  • The compatibility matrix — the single most-linked page on the site, because "will it fit?" beats "what is it?" most days.
  • Guides — longer narratives like the RackMate build guide that walk through a whole project instead of one product.
  • Support pages — the troubleshooting and downloads sections that catch whatever the product pages do not cover.

Why a blog, then?​

Product pages have to stay factual and stable: a specification is either right or it is not. Experiences, build stories and lessons learned do not fit that format — they are opinionated, dated and conversational. Giving them a separate stream keeps the reference pages clean while still letting us share what we learn. That is exactly the split you are looking at now.

A note on authorship​

Some posts here are drafted with AI assistance and reviewed by an engineer before publishing. Those carry a visible disclosure and a second author byline, so you always know how a piece was written.

Found a gap in the wiki? The troubleshooting pages grow mostly from reader questions — keep them coming.