Use case · Teams
How to build in public without the weekly update chore
Building in public is valuable until writing the update becomes another recurring job. The hard part is reconstructing what changed and why from scattered commits, chats, and notes.
The setup
A simple way to run it in Hark
- 01Document while you build
Add ship, decision, and milestone entries to the project journal as the work happens.
- 02Track meaningful movement
Keep traction metrics and Current state current so updates include evidence and direction, not only a changelog.
- 03Generate a progress update
Select recent entries and create deterministic plain, Markdown, or X-thread copy that remains fully editable.
- 04Link the public project page
Publish selected sections and include the live project page so readers can follow the project beyond one post.
Starter build
Hark’s public project page
Starter builds are coming. Until then, use Hark’s own documented build as the example structure for this setup.
View the public project page placeholder →Common questions
- Can I use this setup for an existing build-in-public project?
- Yes. Import a conversation or brain dump, review the drafted project, and connect the repository when you are ready. You do not have to start from scratch.
- Do all collaborators and agents see the same information?
- They work from the same Hark project and Current state, subject to the workspace and project permissions you choose.
- Can I try this without adding a card?
- Yes. Hark starts with a 14-day card-free trial, and your work remains readable if the trial ends before you choose a plan.