Recently I had a request for a quote from a company who (desperately) needed their Domino-based website pulling in to the 21st century. They needed somebody to re-design the front-end and build a back-end CMS for it.
One of the things they asked me was:
Would you be using XPages?
My reply was along the lines of:
If you really want me to I could, but whether I would or not is something I'll get back to you on.
Nothing came of the project but it got me thinking nonetheless. Is using XPages for a public-facing website a good idea?
I'm still yet to use XPages in any real way but, based on what I do know about XPages, I've formed my own opinions on when they should be used and when they shouldn't.
XPages are fine for use in web-based applications but they'd be overkill and detrimental to performance for a standard website.
Taking a look at the site with Firebug's Page Speed plugin:
Same goes for IQJam.net's and the number of CSS files:
Again, there's nothing going on there that one reasonably-sized CSS couldn't handle.
Apologies to Bruce et al. I'm not picking fault in what you're doing. It's just that yours are the first two XPage-based websites I could think of! That's a good thing, right?
So, my question is twofold -- is it ever a good idea to use XPages for a standard website that happens to be Domino-based and (if so) is there a way to use XPages but without the bloat?
I know I've asked a similar question in the past but I still have no idea whether XPages is a good fit for a website. Next time I get asked to re-design a Domino website and am asked to use XPages I want to be able to reply with more confidence in my convictions.
It all makes me wonder. If XPages is the future of Domino then does that mean Domino has no future as a platform for normal websites?