Build 01 28 entries
Filament Atelier
16 Aug to 13 Sep 2026
A visual page builder for Laravel, shipped as a Filament plugin. Developers define blocks in code, clients arrange them and watch the real page update as they type.
Read from entry 01 →96 entries
The build diary, with the bugs left in
What changed this week, what broke and what I got wrong, written while the work is still happening. These entries are not tutorials, and they do not pretend the work went smoothly.
- Diary entries since 05 Jul 2026
- 96
- Builds with their own series
- 16
- Latest entry, 2026
- 13 Sep
Follow a build
Read one build from the first entry
Every entry belongs to a project, so a series reads in order with previous and next links between entries.
-
-
Build 02 19 entries
GitBasedDocs
10 Sep to 13 Sep 2026
A private docs site that reads Markdown from one GitHub repo. Write in Obsidian, push, and a few seconds later the pages are live for the people you shared them with. Each project is a folder in the repo, and a reader sees only the projects an admin linked to their account. Anyone else gets the same 404 as a project that does not exist. A webhook starts a delta sync that fetches only changed files, a timed recheck covers a missing webhook, and pages are served from SQLite, so reading never calls GitHub. It renders the Markdown Obsidian and GitHub both know: Shiki code, Mermaid diagrams, KaTeX math and Obsidian callouts, plus wikilinks and image embeds. Next.js 16, React 19, next-auth v4 and Drizzle on SQLite, about 9,200 lines of TypeScript, MIT.
Read from entry 01 → -
Build 03 13 entries
MD Kanban
6 Sep to 10 Sep 2026
A kanban board where every card is a markdown file on your disk, built so you can watch what an AI coding agent is doing without asking it. Each connected folder is a project, each subfolder groups work, and each task is one `.md` file whose YAML frontmatter holds status, priority, assignee, due date and labels. Dragging a card between columns rewrites the file, and the agent edits the same files from its side. That is the whole design: Jira and Linear keep state behind an API, so an agent needs credentials and a connector before it can move a card, while a folder is something it can already write to. The repo ships the contract twice, as `AGENTS.md` for any agent and as a Claude skill, and tracks its own remaining build as task files inside itself. Vue 3, Vite, TypeScript and Tailwind v4 over the browser File System Access API, about 1,800 lines, MIT.
Read from entry 01 → -
Builds 04 to 16 34 entries
Filter and sort Filter entries
The log
Every entry, newest first
Showing 1 to 15 of 23
5 entries, 1 build
-
#87 10:05
Filament Atelier Part 25 of 28The editor was a dead end with one exit, and the preview lied about it
Clicking a nav link inside the builder's preview navigated the iframe to that page's live URL. The canvas then showed one page while the section list edited another, with nothing to tell you. Fixing it meant deciding what an iframe inside an editor is actually allowed to do.
Laravel · FilamentPHP · Plugin · Tools · Livewire · UI · UX
-
#86 08:38
Filament Atelier Part 24 of 28The example app stopped using the blocks the package ships
The last request before tagging v0.5.0 was that someone opening the example folder should understand everything without reading the package. That meant the demo site defining all nine of its own sections, which sounded like duplication and turned out to be the most honest thing in the repository.
Laravel · Blade · FilamentPHP · Plugin · Tools · Web Application · UI
-
#84 08:36
Filament Atelier Part 22 of 28The design tokens were correct, and no block was reading them
Building a demo site with a teal brand, I set the primary colour token and the hero button stayed black. The tokens shipped in v0.2.0, the editor preview and the public page both read them, and the two loudest elements in the block library had the colour hardcoded the whole time.
Laravel · Blade · Tailwindcss · FilamentPHP · Plugin · UI · UX
-
#82 08:35
Filament Atelier Part 20 of 28A field nobody can list is a form field with no consumer
Custom fields on a page type are worth nothing until something puts them on a page. Building the block that lists them meant handing every block view the page it is rendered on, which turned out to be a one-line change to the renderer and the most useful thing in the release.
Laravel · Blade · FilamentPHP · Plugin · Tools · UI · UX
-
#80 08:33
Filament Atelier Part 18 of 28Services needed their own sidebar entry, and Filament had already solved it
The ask was simple: services and products should sit in the sidebar next to Pages, not hide behind a dropdown on a page form. The design I approved cost a Filament resource subclass per type in every app that installs the package. Reading the framework source before writing it found the mechanism that removes the subclass entirely.
Laravel · FilamentPHP · Plugin · Tools · Web Application · UI · UX
1 entry, 1 build
1 entry, 1 build
1 entry, 1 build
2 entries, 1 build
-
#48 19:49
Filament Atelier Part 13 of 28What is left, and the things I am not going to build
Seven releases in eight days took Atelier from an MVP to something with a sitemap, structured data, revisions and CI. This is the honest state of it: what works, what is missing, what is deliberately refused, and the two gaps I cannot close by writing more code.
Laravel · FilamentPHP · Plugin · Tools · Web Application · UI · UX
-
#46 19:47
Filament Atelier Part 11 of 28One shell per site was a decision I never made on purpose
Marketing pages want a navbar and a footer, documentation wants a sidebar, a landing page often wants neither. The blocks are identical in all three. v0.2.0 makes the shell a per-page choice, and the test for it caught a bug where a custom layout worked live and crashed in the preview.
Laravel · FilamentPHP · Plugin · Tools · Web Application · Blade · UI · UX
4 entries, 1 build
-
#39 10:02
Vouch Part 6 of 6Where the compliance actually lives
Twenty-nine dashboard screens across three roles, and the four that exist because the EU AI Act and NYC Local Law 144 say they have to.
Figma · UI · UX · Dashboard · AI
-
#38 10:01
Vouch Part 5 of 6Designing a job board at two breakpoints
Fifteen desktop screens and thirteen mobile ones, and the places where mobile had to become a different design rather than a narrower one.
Figma · UI · UX · Website
-
#36 10:00
Vouch Part 3 of 6A Figma system where nothing hard-codes a hex
Four variable collections, 34 components, and the Figma plugin API traps that cost me a 23,828 pixel tall page before I caught them.
Figma · UI · UX · Typescript
-
#35 10:00
Vouch Part 2 of 6Naming Vouch and finding one shape to sign it
One name died to a live check, one shape ended up carrying the whole system, and the palette was chosen by ruling out everything an AI would have picked.
Figma · UI · UX
1 entry, 1 build
FAQ
About the devlogs
Short answers on how the diary is written and how to follow one build.
What is a devlog?
A build diary entry. It covers what changed that week, what broke and what I got wrong. They are not tutorials and they do not pretend the work went smoothly.
Can I follow a single project?
Yes. Pick a build in the filter, or open any entry and use Read the series, which lists every entry on that project in the order it was written.
Is there an RSS feed?
Yes, at /devlogs/feed.xml. It carries the latest 50 entries, newest first.
Work with me
Got a product in your head? Let's put it on a screen.
Tell me what you're building, who it's for and when it has to be live. I'll reply with questions first, then a fixed quote.
Start a project