I recently registered the domain bedtimestories.kids and I'm excited about the possibilities, though I'm still figuring out exactly what to do with it. The idea of creating a dedicated space for cozy bedtime stories feels right, especially since this is a format I already love working with.
My initial thought is to write original bedtime stories and publish them on the site. Nothing too complex or overstimulating, just warm, gentle tales that help children wind down at the end of the day. The kind of stories with soft imagery, reassuring themes, and that perfect drowsy rhythm that makes eyelids heavy.
I'm also considering producing audiobook versions of the stories. Having worked with narration before, I know how much the right voice and pacing can add to a bedtime story. There's something special about a spoken story that a child can listen to in the dark, letting the words paint pictures as they drift off to sleep.
For now, I've put up a simple landing page using Carrd, which I've started experimenting with recently. It's perfect for getting something online quickly, and the one page format works well as a placeholder while I plan the real site. But Carrd's limitations are obvious when you're thinking about a content site with multiple stories, categories, and possibly audio players.
That's why I'm planning to build the actual site using GRAV. It seems like a good fit for this project, offering the flexibility I need to organize stories properly, handle media files efficiently, and create a pleasant reading experience without the overhead of a database-driven CMS. Plus, being file-based means I can keep everything simple and focused on the content itself.
I've really come to appreciate working with GRAV for several reasons, and it keeps proving itself as the right choice for my projects.
The flat-file architecture is probably the biggest draw for me. No database to maintain, no MySQL configurations to worry about, no backup complications. Everything is just files and folders, which means I can version control the entire site with Git if I want to. It's straightforward and transparent in a way that feels refreshing after years of wrestling with WordPress databases.
The Markdown-based content system fits perfectly with how I like to write. I can draft a story or article in any text editor, format it with simple Markdown syntax, and drop it into the right folder. No need to log into an admin panel unless I want to. For someone who writes a lot of content across multiple sites, this workflow feels natural and fast.
GRAV's flexibility is another strength. It's lightweight enough to stay out of your way, but powerful enough to handle complex site structures when you need them. I can start simple and add functionality as the site grows, without feeling locked into decisions I made at the beginning. The modular approach with plugins means I only add what I actually need.
The templating system using Twig is clean and logical. When I need to customize something, I'm working with actual code that makes sense, not trying to decipher some proprietary theme framework. And because everything is file-based, I can simply copy a template file, modify it, and see the changes immediately.
Performance is solid right out of the box. Without database queries slowing things down, pages load quickly. For content-heavy sites like my children's story collections, where I want parents and kids to have a smooth, pleasant experience, this matters.
The learning curve was gentler than I expected. The documentation is thorough, and the community, while smaller than WordPress, tends to be helpful and focused. I didn't need to become a GRAV expert to get productive with it.
