Obsaased Is My Lab Notebook

The Question

For a long time, obsaased.io pointed to a published Notion page. That was a perfectly honest reflection of where my technical ability was, but it was also limiting. I wanted a proper home for the projects I was building, somewhere I could document them in public and build a bit of internet history rather than leaving everything trapped in chats, repos, and half-finished notes.

The experiment was partly about the website itself and partly about the workflow. Could I, as a novice local builder, use an AI coding tool to go from a vague brief to a real custom site, deployed on my own domain, without getting buried in setup and infrastructure?

The Build

This was my first proper local AI-assisted build after doing most of my previous vibe coding in Replit. I used Google Antigravity with a very loose prompt: build me a personal portfolio site, lean hard into design, scrape a few strong 2026 portfolio references from Twitter, borrow one or two distinctive ideas, and push them somewhere more personal. Creatively, I do not think the result is there yet. Functionally, though, it did the job fast.

What mattered most was not the initial homepage. It was the system around it. The site now has a local admin backend, a basic WYSIWYG editor, file-based content, and a deployment path that was simple enough for the AI to walk all the way through. It handled the Vercel hosting flow, then gave me the exact Namecheap DNS records to point the domain correctly. The editor is still clunky, which is why the next iteration is likely no editor at all: a standard experiment structure plus an AI workflow that can generate and publish a post directly.

The Outcome

The most important outcome is that the site is now alive. It is not precious, which makes it useful. I can redesign it, change the structure, publish new ideas, and treat it as a playground without worrying about breaking some polished brand artifact. That changes the relationship entirely.

The bigger surprise was how far a novice user can get with decent prompting in a local environment. The result is still basic, but it moved me from “domain pointed at Notion” to “custom site with publishing infrastructure” quickly enough that the bottleneck is now editorial discipline, not technical setup. That is a much better problem to have.

Tech Stack

React, Vite, local markdown content, local admin tooling, Vercel, Namecheap, Google Antigravity