Making room for regular updates
Once the public pages were taking shape, I started thinking about the work of maintaining them. Adding a project or changing my About page should not require digging through the application every time.
I built a content studio around three collections: Projects, Blogs, and About. Each one has a different purpose, but they share the same idea: make the content manageable while keeping the public website consistent.
Moving content into Supabase
The first version used local Markdown files. They were easy to inspect, but I needed a place where changes made through the admin could persist independently of an application deployment.
I connected the studio to Supabase and kept Markdown for the body of projects and blog posts. Structured metadata holds details such as titles, categories, cover images, and publication status. About uses a structured document for its introduction, experience, skills, and recommendations.
This lets the admin and public pages work from the same stored content instead of maintaining separate versions.
Treating drafts as drafts
I wanted a clear boundary between editing and publishing. A draft should stay private, including when someone knows its URL. Publishing makes an entry available to the public pages; deleting it removes it from those views.
The server checks who is making an admin request, and database access rules limit what public readers can retrieve. I also added revision checks so an older editing session cannot silently overwrite a newer save.
The details around the editor
Writing is only part of the workflow. Cover images need persistent storage, categories need to remain available across sessions, and a preview should resemble the published page.
I added image uploads, category management, and a shared content renderer. Having these pieces together makes updating the site feel more like maintaining a publication and less like modifying a collection of source files.
The result is a workflow I can use as the portfolio grows: write, preview, save a draft, and publish when the content is ready.
