For creators
Publish the project, not the zip
When geometry moves, the bill of materials and the manual should move with it. Studio is the place you keep that record; publishing is how builders find it.
The zip is the problem
A dump of STLs does not tell a builder which hardware to buy, which step uses which part, or what to reprint when you revise a bracket. Slicebuild keeps those together so a release is a project, not a folder.
01
Write the manual in Studio
Add printed parts, then steps. Each step can carry instruction text, hardware, and a 3D view you restage when geometry moves.
02
Publish a URL builders can share
Publishing requires a real step. The public build page is the document: title, steps, bill of materials. The guide player is the assembly view.
03
Revise without orphaning the docs
Swap a part, update the step, republish. Builders following the public URL get the current manual instead of a stale PDF in a Discord pin.
What builders see
Search engines and humans get the same page: headings, step copy, and parts. That is the point of publishing on Slicebuild instead of only hosting files. Read how it works or the builder guide if you want the other side of the bench.
Voron 0.2 · Lower gantry
Questions
- What does Studio actually store?
- Printed parts (STLs), per-step hardware, instruction text, and a 3D view you can restage when a part revises. The public build page is generated from that same record.
- Can I unpublish later?
- Yes. Unpublishing returns the project to draft: it drops off the homepage, Explore, and the sitemap. The files stay in Studio until you change them.