Maker Discussion Fact Notes Template
Prepare verified technical and product facts for a maker discussion so the actual builder can answer in their own words.
When to use this template
Use this when a maker expects questions about a real project and needs factual references, without generating a scripted persona or posting text.
Choose another approach when: You want to invent the maker’s experience, provide paste-ready HN prose, or prepare persuasive claims unsupported by the actual build.
Gather these inputs
- The maker’s actual contribution and project history.
- Verified behavior, architecture boundaries and known limitations.
- Public references safe to share and private information to exclude.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
For a fictional checklist tool, the builder records that exports contain text only, the public demo uses sample data and client authentication is not part of the current prototype. They also note why a local-first experiment was chosen, if that was their real decision. When asked about collaboration, the maker can consult verified facts and answer honestly in their own words. The notes do not invent a dramatic building story or turn a planned synchronization feature into an existing capability.
How to use it
- Record facts the maker can verify from direct work or safe public evidence.
- Separate actual decisions and limitations from plans and unknowns.
- Use the notes for preparation; follow each platform’s rules when writing any final contribution.
Check before using it
- No fictional experience is assigned to a real maker.
- Private architecture or credentials are not included in public references.
- Preparation notes are not treated as permission for automated or generated posting.
What to measure
Assess whether the maker can answer factual questions accurately and acknowledge unknowns. Preparation does not predict reception or imply that an external community endorses the project.
Research and sources
The sources support personal substantive discussion and accurate information. These are original factual preparation fields, not generated HN comments or an attempt to bypass its writing rules.
- Hacker News Guidelines — checked 2026-10-23. Human-written participation, original sources, substantive conversation and no automated posting or vote solicitation.
- Hacker News: Show HN Guidelines — checked 2026-10-23. Personally built, non-trivial work that people can try; waitlist landing pages are not Show HN submissions.
- Google: Creating helpful, reliable, people-first content — checked 2026-10-23. Original value, useful answers, transparent sourcing and a clear audience.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.