First Build in Public Update
A grounded first post that introduces the work without pretending you already know how the story ends.
Use this when
You have chosen a project, created one small artifact, and want to tell people what has actually begun.
The template
I have started working on [literal description of the project].
It is for [specific person or situation] who needs [specific outcome].
The first version currently does [what exists today].
I am starting with this because [observation or personal reason].
Over the next [time box], I want to learn whether [open question].
My next step is [small action].
[Link, screenshot, or demo]
If you have experienced [specific situation], I would like to know: [one focused question]?A filled example
Here is the same structure as a complete update, ready to adapt rather than publish word for word.
I have started working on a small decision log for open-source maintainers.
It is for projects where an old issue explains more than the current documentation. The first version is a Markdown template and an index page. I am starting here because I repeatedly remember what changed in code but forget why an alternative was rejected.
Over the next two weeks, I want to learn whether maintainers will write a three-minute decision note after a meaningful change. My next step is to use the template for one real routing decision.
If you maintain a project, where do you currently record decisions that are too small for an RFC?Make it yours
Delete any line that does not add information. Replace broad labels such as “founders” or “creators” with a situation you can picture. Add only one question.
Before publishing
- [ ] Something already exists.
- [ ] The description is literal.
- [ ] The time box and question are honest.
- [ ] The evidence contains no private information.
- [ ] The reader knows how to respond.