When You're a Rails Developer But Your Client Wants WordPress
Posted by Roger Jin on May 24, 2017
Suppose you've built a Rails app for a client. A couple of months after launching their MVP, your client wants to ramp up their marketing and they ask you to add a blog to their website. "It'd be great if it were WordPress", they tell you. "Oh, and our SEO consultant tells us it should live on our primary domain versus a subdomain."
The thought of WordPress sends shivers down your spine, but you start quietly doing some research on your options.
Integrating WordPress into your Rails app is impossible, but if you run WordPress (or a similar blogging solution like Ghost) separately it'd require hosting and have to live on a separate subdomain, which will cause great dissapointment to your SEO-enthused client.
You explore the workaround of setting up a reverse proxy, but it looks extremely unpleasant. And even after all that trouble, you'll still need to figure out how to customize templates to get the design to match your beautiful Rails website–you wonder if they could share the same layout and CSS...
Determined to find something that can integrate into your Rails app, you scour Github for open-source blog engines. You hop from one promising repository to the next. The first project you find looks good but hasn't been updated in three years. Another requires adding a bunch of bloated database tables to your already over-burdened database. Your hope begins to fade...
If this situation sounds familiar to you, you're not alone.
It's why we created a blog engine and CMS that integrates with Rails in one minute. Friendly UI for your clients, zero maintenance for you, and did we mention it integrates with Rails in one minute?
Don’t miss a single post
Get our latest articles, stay updated!