Yep, I went there. Let’s hope this doesn’t start a religious war.
So, SmallSpec is at the very-rough-internal-prototype stage. My plan has been to develop the product in ASP.NET MVC (Razor), primarily because that stack is in my own personal wheelhouse enough that I can actually review and vouch for the code, even if I didn’t write it myself (which I haven’t, and probably won’t).
But then I got to thinking - if I’m willing to cut the umbilical enough to not write the code, maybe it would be OK for me to not even understand the code? Maybe it would be OK for me to be purely a businessman on this one, and not be an engineer at all? It’s still early enough that I could scrap the work we’ve done and go a different direction if there were sufficient benefit to doing so.
And that sort of thinking led me to wonder if it was possible/wise/manageable to build my Saas app on top of WordPress?
The pros, as I see them, are that there’s already a sound membership/user/authentication system in place. There’s already a sound system in place for plug-ins and extensions. There’s already a sound system in place for theme-ing (which might come in handy for letting customers theme their spec sites for visiting clients).
But what I don’t know is whether or not all that equates to being a good place to bolt an app onto.
The cons - well, con - is that I have a deeply-held, seething hatred of WordPress. Every. Single. Time. I try to do anything with WP it seems 10x more difficult and 10x less obvious than it needs to be, despite everyone else marveling at how simple and obvious everything is in WP. But hey, if I’m not building it, maybe my personal struggles with WP are moot.
So, questions for discussion:
Have any of you built your Saas app on top of WP?
How did you do it without customizing any WP core code?
What kid of troubles did you encounter?
What were the primary benefits (as you see them)?
Would you do it again?