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 18
5 entries, 1 build
-
#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
-
#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
1 entry, 1 build
4 entries, 1 build
-
#47 19:48
Filament Atelier Part 12 of 28Building a demo blog route found a bug older than the feature
v0.3.0 adds structured data: a JSON-LD graph on every page from three sources. While proving that a host app's own blog route could share it, the route 404d. Atelier's catch-all had been registered ahead of every route the application defines, since the first release, and the docs promised the opposite.
Laravel · FilamentPHP · Plugin · Tools · Web Application · SEO · Blade
-
#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
-
#43 19:41
Filament Atelier Part 8 of 28The config invited you to delete your own head tags
A social share image was not showing up. The render path turned out to be correct and the tag was never reaching the page, because the layout had been replaced. Every meta tag lived inside Atelier's own layout view, and a config key openly invited you to swap that view out.
Laravel · FilamentPHP · Plugin · Tools · Web Application · Blade · SEO
-
#41 19:39
Filament Atelier Part 6 of 28The audit found four blockers and one 200 that should have been a 404
I read every task file against the actual code instead of against memory. Four things marked as done were not, and each was quietly blocking a later feature. Then a nested URL turned out to return 200 with the wrong page rendered, which is worse than the 404 I was expecting.
Laravel · FilamentPHP · Plugin · Tools · Web Application · Blade · Tailwindcss
2 entries, 1 build
-
#31 04:51
Filament Atelier Part 2 of 28Three bugs, one mistake: reading Livewire state instead of Filament's
Rich text saved a TipTap document into the database, file uploads saved an empty array, and then uploads stopped reaching the disk entirely. Three separate-looking bugs, all caused by reading a Livewire property directly instead of letting Filament dehydrate its own form state.
Laravel · FilamentPHP · Livewire · Plugin · Blade · Tools
-
#30 04:50
Filament Atelier Part 1 of 28The preview problem I planned for was not the problem
A live preview that renders the real page on every keystroke sounds expensive, so the plan parked per-section rendering as the eventual fix. Then a twelve-section render measured 16ms, the whole optimisation became unnecessary, and the actual difficulty turned out to be somewhere else entirely.
Laravel · FilamentPHP · Livewire · Blade · AlpineJS · Plugin · UI · UX
3 entries, 1 build
-
#23 10:28
LaralCN-UI: A shadcn-style copy-and-own Blade component system for Laravel Part 6 of 6LaralCN-UI docs for agents: llms.txt and a Copy Page button
Pasting a documentation page into Claude Code means pasting a sidebar, a theme toggle and a footer. The docs site now serves a second channel: an /llms.txt index and a .md twin of every component page, generated from the same registry the HTML reads. Plus the route that quietly ate its own suffix.
LaralCN-UI · Laravel · Blade · Tailwindcss · Claude Code · Claude · ShadCN · Frontend · Tools
-
#22 09:50
LaralCN-UI: A shadcn-style copy-and-own Blade component system for Laravel Part 5 of 6LaralCN-UI 0.4.0: ten components, nine without JavaScript
The registry goes from 25 components to 35. A toggle that is a checkbox, a slider that is a range input, a hover card that is pure CSS, and a carousel that keeps working with its script deleted. Plus the three bugs that only turned up once I stopped reading the markup and started clicking it.
LaralCN-UI · Laravel · Blade · Tailwindcss · Javascript · ShadCN · Frontend · UI
-
#21 09:49
LaralCN-UI: A shadcn-style copy-and-own Blade component system for Laravel Part 4 of 6LaralCN-UI 0.3.2: two bugs the test suite could not see
Every card in the registry drew a black border, and every modal opened with a backdrop that was not there. Both bugs lived in the theme rather than the components, both passed 105 tests, and in the second one the computed style was correct while the screen was blank. What Tailwind v4 changed, and why a colour function can parse and still refuse to paint.
LaralCN-UI · Laravel · Blade · Tailwindcss · CSS · ShadCN · Frontend · UI
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