This is what your blog would look like, on Directus.
Every post below was created in the Directus admin (open the editor on the right), written in Markdown, and rendered through this Astro frontend. Built in 90 minutes from an empty Supabase schema.
demo@gautamkhorana.com / directus-demo Read-mostly demo. Click around, try the rich text toolbar, see how scheduled posts work. Real builds: $8,000-$19,000 USD (£6,000-£15,000), 2-3 weeks.
4 posts published
- founder
Why I still write code as a co-founder
The conventional advice is that founders should stop coding once the team is large enough. The conventional advice is wrong for the kind of company I am building.
- engineering
The Monday-style admin pattern, in three components
Inline editing, optimistic saves, toast notifications. Three components that turn a generic CRUD admin into a delightful editing surface.
- opinion
How I think about headless CMS in 2026
Picking a headless CMS in 2026 is a different exercise than it was three years ago. The right answer depends on three questions, not vendor features.
- product
Welcome to the Directus blog demo
A simple demonstration of the standard Directus blog pattern. Markdown body, scheduled publishing, image uploads, the works.
What you are looking at, technically
- CMS: Directus 11.17.4 on Railway (Hobby plan, $5/month)
- Database: Supabase Postgres (free tier)
- Frontend: Astro 5.1, statically generated, deployed on Netlify
- Markdown rendering:
markedat build time - Schema: one table
demo_posts, no relations, deliberately minimal - Editor experience: Directus's
input-rich-text-mdinterface — Notion-like WYSIWYG over a Markdown body field - Total build time: 90 minutes from empty schema to this page
What changes for a real client build
A real deployment adds:
- Categories and tags as separate tables with proper m2o / m2m relationships
- Authors table linked to
directus_usersso each post tracks the editor - Image upload library backed by S3 or Supabase Storage
- Scheduled publishing via a Directus Flow (cron-trigger)
- Roles and permissions so contributors, editors, and admins have different access
- SEO fields (meta title, meta description, Open Graph image) per post
- Revision history and one-click rollback (built into Directus)
- Search via Algolia or Pagefind, integrated into the frontend
None of that is theoretical. All standard Directus features, configured in the admin, no custom code.
When you're ready
Book a 30-minute call. Tell me your editorial team size, your existing CMS, and your timeline. By the end of the call you have a stack pick, a price, and a delivery window.