15 ms·
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 easi
by whalesalad 13y ago
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.
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?
rails g model Post author_id:integer title:string body:text
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.
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: https://www.ruby-toolbox.com/categories/A_B_Testing https://www.ruby-toolbox.com/categories/A_B_Testing
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?
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.
- raheemm 13y agoExample, 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. Exactly, that's a great example of why keeping everything in rails seems to make more sense. EDIT: To clarify my app will remain in rails. Just trying to figure out whether my mktg site should be migrated away to wordpress.
- somesay 13y agoI'm still not sure what exactly your plan is. Just moving your landing/marketing page or the whole ecommerce frontend? WordPress is nice if you need a blog or at least a CMS for luser or if you need some framework to build on. Is that the case? Maybe it's a useful abstraction (e.g. uptime, maintenance, development) and maybe it's good that someone without developer knowledge could work on it, but you told it would need a lot of integration work? Sounds like you should create an API then. If you need an API anyway, than this actually would be a great way to test it in a real environment. Otherwise likely unneeded effort. To speak about WordPress plugins, please mind, that most of them are rather simple. Hook some button code and JavaScript somewhere and offer some simple configuration backend UI. Deep integration for any features the user might see often needs custom CSS work, editing the site template or even coding within the plugin. At least that's my experience with my personal requirements. Or to say it in different words: Integrating Facebook buttons isn't that hard anyway, but a professional newsletter would be a lot of work anyway. Also you could likely reuse the plugin code and transform it into Rails code.
- raheemm 13y agoIm looking into moving the marketing page to wordpress. The app is most certainly not moving to wordpress. It's staying in rails.
- debaserab2 13y agoHaving good blogging software is not as simple as generating a data structure. There's plenty to be said for having a good admin UI (that non-developers can easily figure out). The flexibility and depth you get out of the box is not going to be matched by anything you can do yourself in a short amount of time. > You can rebuild ANY feature or plugin in the WP domain very easily in Rails This is just false - there's so many well matured products in the WP ecosystem that would take way too long to quickly develop no matter what language you're using. There's a lot of plugins built specifically in mind for a marketing / brochure type website that have had years of development that you can benefit from immediately (SEO plugins, contact forms, ecommerce..) I'm not suggesting that WP as a frontend is the way to go, but I would not throw it out with the assumption that you will be able to rebuild it easily. I would weight the decision entirely on how much integration will need to be done and what your marketing needs are. A couple of questions I'd ask are: 1) Is there going to be someone constantly tinkering with the site to tweak SEO as much as possible? 2) Will content be frequently updated, or will the site act more as a landing page with just occasional updates? 3) Do you ever need to authenticate a user on the marketing site? (I find cross-application authentication to be one of the harder integration problems to tackle and a good reason to not use a separate CMS system) If it's just a landing page with only occasional updates, building it out as a simple view within your existing app framework may work just fine (or heck, just some static HTML files may fit the bill).