the dots family.
Back to the stories
WORK · FROM THE FAMILY

Dotty helped build the home for these stories.

From a playful prototype to an invite-only publishing pilot: a real example of building with a dot, checking the result and keeping people in control.

Dotty & The Dots Family ↗Sign in to save

From idea to a live pilot

Shared by a community member and reviewed for publication. Experiences are personal; review facts and your dot’s suggestions before acting.
01 / THE STARTING POINT

A familiar little challenge.

The idea was a welcoming place for people to introduce their dots and share useful outcomes. We needed a working prototype to explore the experience before choosing the backend.

02 / A LITTLE HELP

Two heads. One good direction.

We started with Next.js, sample content and the complete browsing and submission flow. After reviewing the design, we added PostgreSQL, Google sign-in, owner-only drafts, bookmarks and a review queue. Development and production data were kept separate. Automated tests and browser checks exercised the publishing flow, including a private revision that must not replace its approved public version. People approved account access, configuration and the final launch.

03 / THE SMALL WIN

A little lighter. A little clearer.

The Dots Family launched as an invite-only contributor pilot on 30 September 2026. Public visitors can browse approved stories; only invited Google accounts can sign in. Stories and profile snapshots become public after a human review. This is an early pilot, not a guarantee of flawless software: broader account testing, operational recovery checks and ongoing maintenance still matter.

TRY A LITTLE INSPIRATION

Help me turn this idea into a small working web app. Start by asking what the first user should be able to do. Build a polished prototype with clearly labelled sample data and test the complete flow. Then propose the simplest backend for real use. Keep test and production data separate; make drafts private and check authorization on every write. Show me what was tested, what failed and what remains uncertain. Ask before new account access, paid commitments or the final production launch. Never put credentials or private information into public examples.

Make it yours. Adapt these instructions to your own needs.

Report a concern about this story ↗

Keep private and confidential information out of public prompts. Always check costs, facts and availability yourself.