EDMONIO
Edmonio Build Lab

What shipped. What failed. What changed.

A public record of projects and experiments, including the result and the lesson. Progress is more useful when the unfinished parts are visible too.

Edmonio.com homepage showing the book launch and personal platform
Edmonio.com · Live
Featured build2026 · Live and evolving

Edmonio.com

One platform for Edmonio's identity, debut book, launch event, pre-orders, reader emails, and collaboration inquiries.

The problem
The personal story, book, event, and business contact paths needed one clear home instead of competing for attention.
What was built
A responsive website with book pre-orders, contact workflows, lead capture, confirmation emails, and cross-platform calendar integration.
Stack
React Router, TypeScript, Hono, Supabase, and Resend.
Main lesson
Clarity improves when every page has one job and every action has an obvious destination.
Open the live project
Experiment archive

Earlier builds, without rewriting history.

These entries stay short until there is enough evidence for a complete case study.

2023Archived

First Browser Extension

The first attempt to turn an idea into a product that other people could install and use.

Result

Launched with zero users.

Lesson

Working code is only one part of a product. Distribution, positioning, and feedback matter too.

2024Experimenting

Full-Stack SaaS Experiments

A series of small products built while learning React, Node, databases, and how complete systems fit together.

Result

Rebuilt the same ideas more than once as the technical foundation improved.

Lesson

Smaller releases create faster feedback loops than waiting for one perfect, oversized launch.

2025Ongoing

Open Source and Building in Public

Published libraries and began sharing the process, not only the polished result.

Result

Moved from private practice to public work that other builders could inspect.

Lesson

Documenting decisions creates trust and makes every project more useful than its final code.

The build loop

How each project moves forward.

The technology changes. The loop stays intentionally simple.

  1. STEP · 01

    Find the real problem

    Start with a specific frustration or need, not a feature list.

  2. STEP · 02

    Build the smallest proof

    Create enough to test the central idea before expanding the system.

  3. STEP · 03

    Ship and observe

    Put the work in front of people and pay attention to what they actually do.

  4. STEP · 04

    Record the lesson

    Keep what worked, name what failed, and use both in the next build.

Have something thoughtful to build?

Edmonio is open to serious collaborations, interviews, and conversations about useful products.

Start a conversation