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 39
12 entries, 2 builds
-
#96 14:15
GitBasedDocs Part 19 of 19Search that quotes whatever you type
GitBasedDocs search moved from LIKE over every page body to SQLite FTS5 kept in step by triggers. Word prefixes and accent folding came with the tokenizer. The real work was quoting input, choosing a stable order, and a backup detail about rowids.
Typescript · Nextjs · Web Application · Tools
-
#93 14:14
GitBasedDocs Part 16 of 19My login rate limit was a lockout button
Five tries per email in fifteen minutes stopped password guessing, and it also let anyone lock a person out with five wrong guesses. The other key read a header the client writes. The same review found that changing your password left your other devices signed in.
Nextjs · Typescript · Web Application
-
#92 14:13
GitBasedDocs Part 15 of 19A failed download that was never going to be retried
Two GitHub calls per changed page against a token allowed 5,000 an hour meant a big vault's first sync would fail partway. Fixing that turned up a worse bug: a file that failed to download was marked as synced along with everything else.
Nextjs · Typescript · Web Application
-
#91 14:09
GitBasedDocs Part 14 of 19Sync said unchanged, and the new project stayed empty
Adding a project to a repo GitBasedDocs had already synced showed an empty project until someone pushed. The check that makes sync cheap was keyed on the branch head, and creating a project does not move the head.
Nextjs · Typescript · Web Application · Tools
-
#90 10:08
Filament Atelier Part 28 of 28Tagging 1.0.0 with four features missing, on purpose
The gate list had thirteen items. Six went in, seven did not, and the tag went out anyway. What the number promises is that the API stops moving, not that the feature list is finished, and conflating those two is how packages sit at 0.x for three years.
Laravel · FilamentPHP · Plugin · Tools · Web Application
-
#89 10:07
Filament Atelier Part 27 of 28Reading my own release checklist found two bugs I had written down and walked past
The gate list for 1.0.0 had eight items under "bugs the audit turned up". Two of them were not tidying: the home page had two URLs with the canonical naming the copy, and any URL typed in the panel went into an href without a scheme check. Both were an hour, and both were about to be frozen behind a version number.
Laravel · FilamentPHP · Plugin · Tools · Web Application · SEO
-
#88 10:06
Filament Atelier Part 26 of 28A script in three layouts is a contract nobody signed
The editor's preview needed a few lines of JavaScript in the page it renders. I put them in the shipped layout, then copied them into two more. Anyone writing their own layout had to copy them too, and missing them broke half the editor with no error at all.
Laravel · Blade · FilamentPHP · Plugin · Tools · Web Application
-
#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
-
#85 08:37
Filament Atelier Part 23 of 28The demo needed a booking form, and a form needs someone to not trust
The example app grew into a whole cleaning company: services with pricing tiers, products with variations, and forms that turn a page into a lead. One rule survived every shortcut the demo tempted me into, and it is the only part of it I wrote tests for first.
Laravel · Blade · FilamentPHP · Plugin · Tools · Web Application · UX
-
#83 08:35
Filament Atelier Part 21 of 28A generated /services page shadowed a 301 I shipped three releases ago
A page type can serve a listing at its own prefix without anyone building a page. That route has to sit ahead of the catch-all to exist at all, which means it sits ahead of everything the catch-all was handling. The test suite failed on a redirect written in v0.2.0, and it was right to.
Laravel · FilamentPHP · Plugin · Tools · Web Application · SEO
-
#81 08:34
Filament Atelier Part 19 of 28The storage shape for custom fields was already in the codebase, one column over
A page type declares its own fields, and the plugin never learns their names. That leaves one question: where the values go, and what happens to the translated ones. I designed a shape, then noticed the SEO column had been storing the same thing correctly since the first release.
Laravel · FilamentPHP · Plugin · Tools · Web Application · 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
3 entries, 1 build
-
#74 18:48
GitBasedDocs Part 8 of 19Who changed this page?
GitBasedDocs pages now show who changed them last, pulled from the GitHub commit list at sync time. The commit id and GitHub link shipped for editors too, then moved to admins only.
Nextjs · Typescript · Web Application
-
#71 18:47
GitBasedDocs Part 5 of 19404, never 403: access control that doesn't leak project names
How GitBasedDocs keeps each client inside their own projects: one access gate, the same 404 for every refusal, images behind the same check, and JWT sessions that still notice a deactivated user.
Nextjs · Typescript · Web Application · Dashboard
-
#70 18:47
GitBasedDocs Part 4 of 19Specs before code: the plan behind a two-day build
The first GitBasedDocs commit was almost all plan: research notes, feature specs and task cards. How that plan was shaped, and the four places reality corrected it.
Tools · Web Application · Claude Code · agents
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