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 6 of 6
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
3 entries, 1 build
-
#20 22:47
LaralCN-UI: A shadcn-style copy-and-own Blade component system for Laravel Part 3 of 6Shipping LaralCN-UI 0.3.0: three ways a deploy can lie to you
The release was tagged, the tests passed, and the live site was still broken. A gitignore line had frozen the deployed CSS eleven commits earlier, the server was running code from before the merge, and my own syntax highlighting took every documentation page down with a 500. What each failure looked like from the outside, and why the last one was the worst kind of bug.
LaralCN-UI · Laravel · Blade · vps · hosting · Tools · Javascript
-
#19 22:46
LaralCN-UI: A shadcn-style copy-and-own Blade component system for Laravel Part 2 of 6LaralCN-UI blocks: installing a navbar and getting a navbar
Every navbar block shipped a full demo page: a min-h-screen wrapper and a hero section that had nothing to do with the navbar. This pass strips them to the header alone, drops Alpine from the docs site itself so it stops proving the opposite of what it documents, and moves syntax highlighting to the server. Including the component attribute that quietly broke the page around it.
LaralCN-UI · Laravel · Blade · Tailwindcss · ShadCN · UI · Frontend · Tools
-
#18 22:45
LaralCN-UI: A shadcn-style copy-and-own Blade component system for Laravel Part 1 of 6LaralCN-UI 0.3.0: components that carry their own JavaScript
Every interactive component in the registry used Alpine.js, which meant copying one Blade file into a fresh Laravel app was never actually one step. 0.3.0 removes Alpine entirely: each component ships a small inline script in the same file, and several of them now need no script at all. Plus the four traps I hit doing it, including a modal that opened invisible.
LaralCN-UI · Laravel · Blade · Tailwindcss · AlpineJS · Javascript · ShadCN · 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