Up next: Node.js with a Microsoft Access backend
I would say it's a pretty good way to separate concerns (disclaimer: I did this exact thing for http://enter.co).
A CMS is a Content Management System, after all... so it makes sense to use WordPress to manage different content types, handle authors, editors, and contributors, manage media assets, schedule posts and generally stuff that a CMS would do well.
Angular, on the other hand, it's awesome for defining presentation and presentation behaviour. It can speed up front-end development a lot, specially if you use directives properly, so it makes sense to use it. IMHO it's a much better bet than using WordPress' theme system.
I see several advantages to this model:
- Better separation of concerns
- More scalability: separating stuff will give you more options to scale just the stuff you need
- Allows you to have a more sensible separation of responsibility: you can have different teams working on the backend and the frontend.
- Makes more sense when debugging (ever got one of those weird blank screens of death with WP that come out of nowhere? won't happen with this approach)
It just seems super counterintuitive to me. But if it works for somebody, good for them.
He's just given you a fantastic list of reasons why - what's your counterargument?
It wasn't an argument, I legitimately wanted to know why someone would go through the trouble.
Also, just to note the JSON side of this will be in the WP core at the end of the year according to this: http://wptavern.com/json-rest-api-slated-for-wordpress-4-1-release
I'd be really interested to understand the rationale behind choosing wordpress as a backend. Was it just to save time? Because of familiarity?
I'd guess because it is such a common "backend". Easy and secure way to set up a CMS that anyone can then edit.
I know that its easy to set up but is it really secure? It was my understanding that WordPress was one of the least secure CMSs due to its popularity and plugin misuse.
I am by no means and expert, but my understanding is the security of the core product is pretty good for what it is. There have been big pushes to enhance the security. If you're careful about which plugins you use and update often the security is good and better than other options.
The issue is it's so popular and there are so many installs out there that aren't up to date with security patches, which makes for lots of low hanging fruit.
Simple, familiar, and has a JSON plugin. I'm sure there are plenty of other CMSs which could do the job.
If you're looking to use WordPress without having to write PHP, another option is Timber. This plugin lets you write your markup in a templating language called "twig". This language actually looks lot like Mustache.
Nice! This is the same system that powers the new PRPL site. We did a little blog post about our experience here: http://prpl.rs/x/ngprpl