Practical reads on shipping, writing a README that lands, and the other small things that make your project go further.
What it means to ship a project on Stardance, what review looks for, and what happens after you click the button.
Pick what you built, get a tailored checklist of what 'shipped' means for that kind of project — from web apps to hardware to OSS contributions.
Structure, must-haves, and common mistakes — the README is the first thing reviewers and voters see.
Set up a public GitHub repository for your project's code and link it back to Stardance.
Small, atomic, well-named commits make your project easier to read, review, and revisit. Here's how.
What to put in a devlog, how often to post, and why this affects voting.
Stardance's hardware track — a 6-day hardware hackathon and expo with Open Sauce in San Francisco.
How to get started with your hardware project — coming up with an idea and advice for working on it.
Get your project ready to ship — required files, repository structure, and the step-by-step.
What the different Outpost project tiers look like, with budgets, points, and examples for each.
Frequently asked questions about Outpost — channels, logistics, and more.
How to earn Super Hardware Builder status — the requirement to qualify for Outpost.