Live data from Hacker News

Ask HN: Should I use Wordpress to power the front end of my Rails web app?

news.ycombinator.com

1–10 of 28 posts

Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#1
My webapp (a loyalty app for ecommerce) is being built in Rails. Currently the marketing site/frontend is also built in rails. My partner who is a marketing expert, is suggesting that we move the frontend to wordpress since WP has a bunch of marketing plugins.

However, moving the frontend away from rails is going to require integrations between wordpress and the rails backend, which is creating a layer of complexity and management overhead.

Im interested in learning what others have done with their webapp's frontend/marketing site?

1. Is it in the same platform as your backend?

2. Did you move it to a different platform such as wordpress? What kind of challenges did you have?

EDIT: Here are some reasons that my mktg partner is suggesting wordpress for frontend:

1. Built in blogging

2. PLugins for Integration with email marketing

3. Plugins for Integration with sales-funnel and AB testing

4. Plugins for social media marketing

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#2
I'd put the marketing site at whatever.com and the app and app.whatever.com.

You then decide what types of information needs to pass between the two systems. Instead of porting your entire frontend you simple build a few API calls and pull those in with WordPress.

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#3
Generally speaking, installing and having an installation of Wordpress is pretty simple. However, my advice would be to keep things as simple as possible, especially since it seems you guys are starting out.

For the frontend, I'd recommend either just having very thin pages in your Rails stack that are fully or at least heavily cached that then ping your API, or relying on something like Jekyll to generate static pages that then do the same.

Eventually, when the project becomes larger and/if you start feeling pain points, you can abstract this frontend layer away from the stack into its own little app. You could also make it its own little Rails or Sinatra app that just serves basically HTML (again, heavily cached, since the dynamic content will come from the backend). I keep recommending keeping it in Rails or Sinatra just so you can use some goodies like layouts, easy caching infrastructure, you're already hosting rails, the asset pipeline.

As for your marketing site, I'd go for something that's hosted elsewhere, like Tumblr if you need a blog, etc. Just try to minimize the things you need to host and support yourselves.

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#4

I'd put the marketing site at whatever.com and the app and app.whatever.com. You then decide what types of information needs to pass between the two systems. Instead of porting your entire frontend you simple build a few API calls and pull those in with WordPress.

this.

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#6
It's important to realize that "marketing site" and "frontend" are totally different things. If it's truly just a informational site, WP is probably fine. But, I would not build your app's UI, or even purchase workflow, in Wordpress and then your real "app" in Rails.

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#7
I'd say go w/ wordpress as a subdomain of the main app, and use the Json plugin to pull in data to your existing design, you can still linkout to the blog, but the main site will be easier to design using the data from the blog. ie. blog.yourappp.com and anywhere you want on the front page you could pull in recent posts or comments using the json api.

That's what I use for my laravel apps.

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#8

I'd put the marketing site at whatever.com and the app and app.whatever.com. You then decide what types of information needs to pass between the two systems. Instead of porting your entire frontend you simple build a few API calls and pull those in with WordPress.

As someone who is a full-time WordPress platform architect, I completely agree with @deathspin here.

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#9
There is a good amount of complexity that gets added when you try integrating rails and wordpress, as you already mentioned.

I understand the appeal of the plugins, but its usually quite easy to work around, what plugins in specific are you interested in?

i.e. Which email marketing and sales plugins are you referring to?

Social media and AB testing are easy to implement in rails or most frameworks for that matter.

Re: Ask HN: Should I use Wordpress to power the front end of my Rails web app?

#10
post #9

There is a good amount of complexity that gets added when you try integrating rails and wordpress, as you already mentioned. I understand the appeal of the plugins, but its usually quite easy to work around, what plugins in specific are you interested in? i.e. Which email marketing and sales plugins are you referring to? Social media and AB testing are easy to implement in rails or most frameworks for that matter.

I dont have any specific plugins. But the initial thought was that instead of coding up integrations with rails for various 3rd party marketing stuff, lets just use wordpress and save ourselves time.
Post reply on HN