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.<p>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.<p>Im interested in learning what others have done with their webapp's frontend/marketing site?<p>1. Is it in the same platform as your backend?<p>2. Did you move it to a different platform such as wordpress? What kind of challenges did you have?<p>EDIT: Here are some reasons that my mktg partner is suggesting wordpress for frontend:<p>1. Built in blogging<p>2. PLugins for Integration with email marketing<p>3. Plugins for Integration with sales-funnel and AB testing<p>4. Plugins for social media marketing
I'd put the marketing site at whatever.com and the app and app.whatever.com.<p>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.
The marketing tools you gain in WP are not worth building your product-core in WP. Anything that you get as a WP plugin is something you could build really easily as your own component in Rails.<p>1. built-in blogging ... everyone and their brother has built a blogging platform for Rails. WP's blogging platform is a one-size-fits-all approach which usually means you only use about 10% of what it's capable of, so having all the extra cruft is just unnecessary. You want a simple blog in Rails?<p><pre><code> rails g model Post author_id:integer title:string body:text
</code></pre>
2. integration with email marketing – the plugin is only going to get you half-way there. On either platform, rails or wordpress or anything else, you still need to build the component that will take your specific business data and turn that into actionable emails. Example, email users who joined in the last 30 days who have not used our service. That is something you need to build yourself for your specific product no matter what back-end you are using.<p>3. Sales-funnel and AB testing – Mixpanel or Google Analytics will give you the funneling. AB testing can be done with your own solution to solve your exact problems, or check out the variety of gems that help make it easy: <a href="https://www.ruby-toolbox.com/categories/A_B_Testing" rel="nofollow">https://www.ruby-toolbox.com/categories/A_B_Testing</a><p>4. Social media marketing ... again throwing the idea around that you can click "install plugin" and have all your bases covered here is not very realistic. What do you mean by this? Automatically tweet or post to fb based on certain events on the app? Auto tweet/post your blog posts?<p>Either way, I'd argue against doing anything with Wordpress other than a static blog.yourdomain.com. You can rebuild ANY feature or plugin in the WP domain very easily in Rails.
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.<p>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.<p>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.<p>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.
We actually recommend exactly this to many of our customers. Unless the marketing homepage needs a lot of dynamic app-database driven content we usually recommend installing wordpress on www.domain.com and rails app on domain.com.<p>when user is not logged-in, domain.com redirects to www.domain.com.<p>this setup saves a lot of time on static pages management and adds quite a bit of marketing power.
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.<p>That's what I use for my laravel apps.
There is a good amount of complexity that gets added when you try integrating rails and wordpress, as you already mentioned.<p>I understand the appeal of the plugins, but its usually quite easy to work around, what plugins in specific are you interested in?<p>i.e. Which email marketing and sales plugins are you referring to?<p>Social media and AB testing are easy to implement in rails or most frameworks for that matter.
I'm currently working on a project that employs this concept; we use Rails for the heavy lifting, registration, payments, etc (lots of complex stuff), and we use Wordpress to allow our client to easily create beautiful things.<p>The truth of the matter is that making a rails app that covers the flexibility that Wordpress allows (including things like Yoast's seo plugin, for instance) is just infeasible in Rails. The newest update to Wordpress is also quite beautiful.<p>I've been building on Rails and Wordpress for a while now, and have yet to see a full featured solution to flexible content management that equals or surpasses WP. I have yet to see something that makes data transformation and api creation as easy as rails does. (These are gross overstatements, but the point is that the two tools are very different in key ways, and can be used to complement each other if those differences are respected.)
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.
I've found the best approach is to use something like middleman to build the front end / marketing site. Good ol static pages and the rails app is isolated from the static page. Middleman also has a blogging plugin which makes I easy to keep it updated. Doing SEO is also straight forward since they are just static pages