🧪 This is a TEST article. It exists only to preview how the Blog feature looks and behaves. The story below is illustrative, not a real build report — please delete the file blog/2026-09-20-five-lessons-10-inch-rack.md after testing.

✍️ This post was drafted with AI assistance and reviewed by the DeskPi team before publishing. It shares personal build experience — treat it as a story, not a specification sheet.

Last month one of our engineers finally moved a small pile of Raspberry Pi boards from a desk drawer into a proper RackMate T1 10-inch rack. The build itself took an afternoon; the planning took longer, and that is exactly the point of this post. Here are the five lessons that saved us the most time — plus the two mistakes we made anyway.

Lesson 1: Start with a parts plan, not a shopping cart​

Our first instinct was to order "one of everything that looked useful". The better instinct came later: sketch the final layout first, count the U positions, and only then order the trays and panels that layout actually needs. The compatibility matrix did most of the heavy lifting here, because it answers the only question that matters before checkout: does this combination of board, tray and rack actually fit together?

Lesson 2: Airflow is decided before the first board is mounted​

We mounted everything first and thought about airflow "later", which is how "later" becomes "never". The fix was simple: decide the front-to-back air path on day one, group the hotter boards near the fan side, and leave the vented panels where air actually needs to move. After the rework, idle temperatures dropped noticeably within a few minutes of the fans settling in.

Lesson 3: Cable management is a habit, not an afterthought​

The 3D-ring cable management set only works if you install rings as you wire, not after twelve cables have already braided themselves into a single organism. Route, label, move on. Future-you, holding a serial console cable at midnight, will be grateful.

Lesson 4: Watch the thermals before you close the panels​

Before the panels went on, we spent a lazy ten minutes watching idle temperatures on each node, just to have a baseline:

watch -n 5 vcgencmd measure_temp

It is not a lab measurement, but knowing the "normal" idle number for each board makes it obvious later when a fan fails or a vent gets blocked. Most of the "my Pi is slow" mysteries we see in troubleshooting trace back to heat nobody measured until it was already a problem.

Lesson 5: Document the build as you go​

Every time we skipped writing down a step, we paid for it during the first upgrade two weeks later. A photo per stage and one line per decision — layout, air path, power assignments — turned a two-hour "which cable was this again?" session into a ten-minute swap.

What is next​

The rack now hosts a five-node cluster, and the second rack is already in planning. If you are building something similar, the RackMate series overview is a good starting point — and if you run into trouble along the way, the troubleshooting pages cover the common failures we and our users see most.

Have a build of your own? We would love to feature reader builds in a future post.

🧪 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.

🧪 This is a TEST article. It demonstrates a Q&A style post with an image and dual authorship. Please delete the file blog/2026-09-06-top-5-rack-questions.md after testing.

✍️ This post was drafted with AI assistance and reviewed by the DeskPi team before publishing.

We keep an eye on the questions that land in our support inbox, and a clear pattern shows up: most confusion about compact racks comes from the same five places. Here they are, with pointers into the wiki where the full answers live.

1. "Will a 10-inch rack actually fit on a desk?"​

That is rather the point — the RackMate series is designed around desk-scale homelab builds. Measure your desk edge to edge, then compare with the dimensions listed on each rack's product page before ordering.

2. "How do I know which tray fits my board?"​

Start from the compatibility matrix. It maps boards to trays and shelves so you do not have to guess from photos.

3. "Do I need the enclosed version?"​

Depends on your priorities. Open frames make swapping nodes trivial; enclosed racks keep dust out and look tidier on a shelf. The product pages for each frame list what ships with it.

4. "What about power — one brick per board?"​

There are tidier options: see the PDU entries in the accessories overview for centralized power distribution built for this rack size.

5. "It got loud / hot — what do I check first?"​

Work through the thermal steps in troubleshooting — in most reported cases the fix is airflow layout, not the fans themselves.

These five cover most of the inbox. For anything else, the FAQ pages are the place to start.