BUILD NOTE
A prototype page has a different job from a store page. It does not need to sell a finished product. It needs to explain what is available now, what kind of session to expect, and where the work is still rough. That is why Diligesker’s Lab keeps project notes next to each playable route.
Practical note
Project notes are especially useful for small games because the game loop may be compact. A visitor can read a short overview, understand that Netherguard is a deduction session or that Block Smash is a survival arcade run, and decide whether to launch the build. Without that context, a short prototype can look smaller than it really is.
The best notes include current status, controls, limitations, credits, and a “what may change next” section. Those sections make maintenance visible. They also separate original project explanation from generic game-category descriptions copied from elsewhere.
For this lab, a project note should be updated when a visible behavior changes. If loading feedback improves, controls move, screenshots are replaced, or a known limitation is fixed, the page should say so. The page then becomes a record of the public build, not just a static description.