My Local-Only Admin Dashboard Adventure

If you could peek under the hood of my blog, you would notice a tiny piece of magic happening during astro dev.

I built a lightweight, local-only admin dashboard I built to manage my posts without the bloat of a full CMS.

The goal was simple: I wanted a place where I could write, preview, and save posts straight from my development environment, reading and writing files directly to disk. No remote servers, no complicated setup — just a smooth workflow while building my blog.

Why an admin dashboard at all?

It started as a thought experiment which inspired some of my previous writing about the future of content management systems here

Editor research: to MDE or not to MDE?

I explored a few different editor options. I looked at Markdown editors, WYSIWYGs, even some full-blown React-based MDEs. Each one had pros and cons.

In the end, I defaulted to a simple . It’s unassuming, works everywhere, and lets me handle autosave, slug editing, and preview rendering manually. For now, simplicity wins — the goal is not feature overload but a clean, understandable workflow.

Slugs, autosave, and the tiny details

It’s not just about writing text. The goal is to track post metadata, including title, description, tags, published state, and slugs.

A lesson I learned along the way: slugs are tricky. Initially, every title change was generating a new file — a headache. After some adjustments, I implemented:

• Manual slug editing so users can preview and control the filename.
• Autosave that only triggers for existing posts, leaving new posts for manual saves - (then i disabled it for now because astro hot reloads after every save - gotta look into that).
• File renaming on save when the slug changes, keeping the workflow smooth and avoiding duplicates (this is still a work in progess).

$$ Stepping stones to the CMS

I see this as more than just an admin dashboard. It’s a prototype for a future CMS that’s developer-friendly, lightweight, and flexible. By working directly with files during dev, I can experiment with post structure, frontmatter parsing, and preview rendering — all while thinking about what a CMS could be in 2026 and beyond.

It’s a sandbox for ideas. I’m free to experiment with:

• Markdown rendering pipelines
• Frontmatter management
• Tag handling and metadata
• Smooth live previews

What’s next?

I’m thinking about of things like:

• Optional integrated Markdown editors
• Better Preview/Edit experience
• Folder Awareness/Configuration
• What the path to Production looks like
• Making it Available as npm package (super excited for this one)

And a whole bunch of other stuff..

But for now, the local-first approach gives me speed, control, and clarity.

It’s a tiny admin dashboard that let’s you create and edit .md files in your Astro site.