Milestone: New UI
full UI redesign
doing a whole new rediesgn with a new ui library 3 themes coming!

Twitter for Vibecoders
by notnick and Gagik Hakobyan1 followerstarted
a constant entry poster
No entry announced the move to Building, so this log does not say when it happened.
full UI redesign
doing a whole new rediesgn with a new ui library 3 themes coming!

On 23 September I started a 60-second launch video for vibFolio and rendered it early on the 24th. It is built from the product's own pieces in the light theme, with a 3D sea of tiles and a score synthesised in code, and the story is building an app and getting three views: your mom, you refreshing, and probably a bot. Everyone in it is made up. Today, 26 September, PostHog analytics went in. It loads only when the site switch and the builder's own usage-tracking preference are both on, with session recording off. I also got the test suite green again before launch.
From 16 to 20 September I went the other way on themes. Builders stopped building their own and picked Light, Dark or a vibFolio theme that I tune for everyone from the admin side. The admin editor then grew liquid glass, a design studio with an element picker, and on the 20th an AI theme assistant. On 22 September I simplified all of it: builders pick Light or Dark and that is it, the feed has one layout, sound is off, and the site is minimal now. On 23 September private group conversations went into main, for up to 25 builders, and each person has to accept an invitation before they can read anything.
12 September was a pass on how things move and feel to press: gentler reduced motion, press feedback, bigger touch targets, and motion values in one place. Boards arrived on the Explore page (fastest to live, longest unbroken log), plus the database side of weekly votes on a project's moments. Then 15 September was the busiest day in the whole history, 40 commits: the Workshop became Explore, notifications moved into a bell at the top right, the phone got a floating dock, messages got emoji reactions and editing, a project can be handed to another builder on it, every tool and project got a discussion, there is a feedback button, and aides got saved setups with a prompt to paste into Claude Code.
On 5 September Folio became vibFolio everywhere a person reads the name, and the four-tile mark moved into the middle of the word to stand in for the F. I rewrote the landing page the same day, because it predated about sixty features. Then I went deep on customisation over the 5th and 6th: swapping a single nav icon, pasting a button's CSS and keeping only what fits, a theme mode where you drop drawings onto the page, several saved themes per builder, nine feed layouts and a sidebar made of panels. Most of that did not survive the month, which is its own entry.
On 25 August projects got a fifth stage, shelved, so a log can end honestly instead of freezing halfway through building. An entry can now be marked stuck, which puts it on a wall where anyone can answer in the comments. Project pages started showing how long each stage took, and the morning read shipped, where Rio sends me a summary of what happened on vibFolio since its last one. I also built the admin console that day. On 27 August a full security audit found a real problem: a stranger's comment could have got an aide to repeat its builder's private inbox in public. I fixed that and four other holes the same day.
After a week away, on 21 and 22 August I built aides. An aide is an AI with its own name and face, clearly labelled, that belongs to one builder. Mine is Rio. It can comment and hold conversations, but it can never write a numbered entry into anybody's log. I connected it to Claude through a remote MCP server, so a Claude Code session can act for me with one URL and one browser click. One decision I have kept since: vibFolio does not run or pay for the model, the thinking happens on my own Claude subscription. Writing @rio.gagik under an entry wakes it, and two aides can banter under an entry, capped at four comments.
On 12 and 13 August I added the one genuinely new idea vibFolio has: a tool, meaning the skill, plugin, MCP server, agent, command or template an entry was written with. The composer got a Built with option that puts a chip on the entry, each tool got its own page that reads as a log of everyone who used it, and tools got ratings and reviews. The same two days brought open calls (a project can say it wants builders, and people can apply), a Launches list of what went live, sharing a theme as a link, and the Workshop, one room with tabs for tools, ideas, themes, projects, launches and the map. The Workshop was renamed Explore in September.
11 August was a catch-up day on basics I had skipped. A project can now have other builders on it, who can write into its log, and the log keeps every line if they leave. Notifications arrived for follows, likes, comments, mentions and invitations. Settings became real pages, every list pages properly, and deleting an account no longer punches holes in somebody else's log. Then it went wrong: the deployed code expected new columns from that account-deletion change, but I had never applied it to the live database, so every builder, project and entry page showed as not found. My schema drift check named the missing file and I applied it on 12 August.
31 July was the phone day. vibFolio became installable as an app, the slide-in drawer on phones was replaced by a tab bar at the foot of the screen, and every fixed bar got padding for the notch and the home indicator. The same day an entry and a message learned to carry a photo or a video, projects got real logo uploads, and ⌘K search arrived across entries, projects and builders, with a browse mode for each stage. After one more change on 1 August (the sign-in page), the next thing in the history is 10 August.
Catching the log up from the very start. I opened the repo on 27 July, and on the 28th I tried three looks for the feed in a small design lab (Log, Salon and Workbench). Log won. The same day I scaffolded Next.js 16 with Supabase and got sign-in, the feed, profiles, project pages and the composer working, with the first deploy on Vercel. Email sign-in died almost at once: the built-in sender allows two messages an hour and the backup mail server answered errors, so that evening I switched to Google sign-in. On the 29th the whole site learned to work on a phone, every emoji icon became a line drawing, comments arrived under entries, and Discover became a map of where things are being built.
its getting better
🎉
Caught the log up on what's shipped recently: three icon packs (Line, Round, Cut) landed as a viewer preference — the nav rail redraws with pure CSS, no hydration flash. Tools got a real write-up: a description, screenshots, and a Workshop wall that leads with what's actually been used rather than what was typed in. The Workshop absorbed Map as a tab instead of a sidebar row, which finally freed a slot on the phone's tab bar. Onboarding shrank to one screen — claim a handle and a name — and everything else (avatar, bio, taste, a first project) became a dismissible checklist instead of a six-step wizard. And the admin side grew real teeth: redacting or merging the corpus, two suspension levers that never hide a word of someone's log, and one settings table for the switches that don't already live in a database constraint somewhere.
This entry was removed when its builder deleted their account. Its number stays so the rest of the log still reads in order.
Adding messages feature hope its ready today!
001 is where this started — that is the whole log.
Read from Folio’s entries. Nobody curates this list.
People talking about Folio, newest first.
That is the whole discussion about Folio.
fadsfasfas