-
-
VaporCMS Editor
-
VaporCMS SEO Warnings
-
VaporCMS Table of Contents Generation
-
VaporCMS Localizations
Inspiration
As a previous founder of another startup heavily reliant on content marketing, I was surprised to see how little focus was given to the content editing experience in existing headless CMSes. We often found ourselves drafting content in Notion, only to spend hours transferring it to our CMS. Collaborating with other content writers was equally frustrating. Not to mention the countless issues when working with localized content. Most CMSes don’t even offer a way to localize content, and the ones that do, charge an arm and a leg for additional locales.
This was simply unacceptable to us, and we knew there had to be a better way, which is why we decided to build it ourselves. VaporCMS attempts to solve all these issues and more. We focus only on your blog content, leaving the rest of the site up to you. This means you don’t need to spend hours configuring your CMS models and data structures, and you can get started right away with writing content.
Because we understand how important it is to have proper SEO optimizations baked into your content, we have included built-in checks that will warn you whenever something needs to be optimized. Be it image sizes, formats, alt texts, meta tag lengths and a lot of other small details which we’ve learned along our journey of building a content-focused, bootstrapped SaaS.
What it does
Helps in managing your content across all stages, including publishing.
How I built it
Using Next.js, Node.js, Typescript and PostgreSQL.
Challenges I ran into
The content localization and publishing were a little troublesome, as you have to ensure the content can be rolled back.
Accomplishments that I'm proud of
We've built a CMS that I'd be happy to use.
What I learned
Building a product that you'd use to solve your particular problems is hard.
What's next for VaporCMS
We have exciting features on our roadmap that would tremendously decrease the time it takes to write articles.
