Split your stack, marketing VS app

Making of the Peeks blog

Peeks now has a blog! I'll be announcing new features, tutorials and other happenings here, and hopefully keep you up to date with everything that's going on. I'll also be sharing my personal journey building it, and hopefully help some of you learn some new stuff too.

First lesson: split your stack.

‍

Marketing VS application

The makers among you are always interested in what stacks others use, and why, so lets' cover that first. The Peeks blog is currently running on the Webflow CMS. The Peeks SAAS application runs on NextJS on Vercel.

‍

I chose Webflow for my marketing site, because of an interesting thread on Twitter recommending you keep all your marketing related content on a platform that would be accessible for non-techie people. The idea is to have your landing page, blog and documentation running on a simple to use WYSIWYG platform that normal people can use, and having your actual SAAS application and crazy spaghetti code run on a separate subdomain.

The reasoning behind this setup is simple; to spare yourself massive headaches in the future.

‍

Firstly, no one trying to get a new product up and running should be spinning their wheels building custom blogging solutions or hand-rolled landing pages. Seriously, these are solved problems. Just making time to write blog posts is hard enough, you don't need to be fighting code and build systems on top of that.

‍

Secondly, if you need to delegate some of your marketing related tasks at a later stage, you would need common blogging related features like access control, permissions and editorial flows. Believe me, you do not want to be spending time trying to figure all of that out. Especially when you're get to a stage where you already feel you need to onboard some help.

‍

Third, you don't want to be unbundling landing pages and blog posts from your main SAAS application at a later stage. This will introduce a lot of risk to your product, and unless you have a million integrations tests and a QA team watching your back(which indies don't), you'd be playing with fire. Nah, just keep all of that separate from the get-go.

‍

OK, that's it for now

Thanks for checking out the blog. I hope it will become a valuable resource for you in the future.

‍

‍