./show-and-tell is the room where you post what you built with PaellaDoc — and, if you want it, the path to a permanent Founding 50 badge. The rule: include evidence — screenshot, screen recording, or public repo. For Founding submissions, attach your .paella file and mention @jlcases. Program details · /showcase.
This category serves two purposes: the community sees what PaellaDoc enables, and the first 50 individual builders earn a permanent Founding 50 badge. It’s not a marketing wall. It has four rules.
Rule 1 — Include evidence
Don’t say “I built a CRM with PaellaDoc”. Show:
- At least one screenshot of the running app
- The Golden Gate evidence pack (or a screenshot of it green)
- If possible, the public repo link or the live URL
- Bonus: a short Loom/video walking the flow
Posts without any evidence get gently moved to ./help so we can figure out what you actually built.
Rule 2 — Say which persona you came in as
Tag your post with whether you used the I have a repo, New project, Product Manager, or No-coder path. This is gold for other people landing on PaellaDoc — they want to see what their persona has shipped.
Rule 3 — Be specific about what was hard
The most valuable Show & Tell posts say “this part the engine got right first try, this part took 4 iterations, this part I had to write by hand because the gate kept failing for X reason”. That trains the community. “Everything worked perfectly” tells us nothing.
Rule 4 — For Founding 50 status: attach .paella + mention @jlcases
Founding 50 is opt-in. If you want the
badge, two extra things must be in your post:
- Your
.paellafile attached — the artifact PaellaDoc produces when you build. This is the proof. Posts without it stay as community Show & Tell but don’t qualify for Founding. - A
@jlcasesmention somewhere in the post — that’s the signal “review me for Founding”.
I review within 48h. Approved → automatic Founding 50 badge + featured card on paelladoc.com/showcase + 30-min Zoom call with me + alpha access to new Pro features as they ship.
No .paella and no @jlcases? Your post still lives here. It’s still valuable. Just not a Founding submission.
A good template
Title: [Persona] What I built — 1 line description
Body:
- The idea (1–3 lines)
- The setup: engine, method pack, how long it took
- Screenshot or video
- What was hard / what the gate caught / what I had to override
- Repo or live link (if public)
- Attached: your-project.paella ← required for Founding badge
- @jlcases ← required for Founding review
What I (jlcases) will do here
I review Founding submissions (posts with .paella + @jlcases) within 48h. For everything else, I won’t pin every post and I won’t “like” everything reflexively — I reply with concrete questions when something looks interesting or non-obvious. If a build is exemplary, I feature it in the next release notes (./announcements).
The program closes when 50 slots are granted, or on 2026-06-30 — whichever first.