Revision labels are not enough
Knowing that a board is Rev B tells you almost nothing by itself. The real information is the change list, the reason for the change, and the test result that justified shipping it.
A blog post can capture the story around the revision while the project page and product page hold the more durable reference information.
Narrative context matters
Tutorials tell people what to do. Blog posts explain why the team changed direction, what tradeoffs were accepted, and what surprised everyone during test.
That narrative layer turns a documentation site into something closer to a lab notebook than a marketing shell.
The archive should stay easy to host
Keeping the first version static is a pragmatic choice. It lets the team publish now on GitHub while preserving an information model that can later move behind Django without breaking the user-facing structure.