They like it because they're very non-technical people, but totally get spreadsheets. I like it because there's version-control on any changes to the spreadsheet, so tracking updates is easy. Everything is cached in-case Google'd data were to ever be inaccessible, but it's a system that was easy to implement, and has worked well for a couple years without any perceivable negatives.
1. My data is on this spreadsheet: https://docs.google.com/a/mozilla.com/spreadsheets/d/1CXdwQq...
2. I load the spreadsheet's tab "1816064743" as XML: https://github.com/cpeterso/arewee10syet/blob/master/index.h...
3. Then parse the spreadsheet rows and columns here: https://github.com/cpeterso/arewee10syet/blob/master/js/gdat...
4. And display the pretty results on my website: http://arewee10syet.com/
My experience matches this. About a year ago I rigged up Google Spreadsheets as a data source for Middleman in order to streamline content updates from the client throughout development. I learned the hard way to use fuzzy matching when correlating client-editable record names between data sources, but it otherwise worked well for both of us.
I like it so much I submitted it to ProductHunt -> http://www.producthunt.com/posts/data-by-brace
I basically shove whatever random lists of things I need to manage into a shared Workflowy list and then point some server-side PHP at it. It has some crude memcache support and conventions for formatting the content and stuff.
It's handy because it makes it really easy to manage those "extra things" that most people don't have time to model in a CMS: sidebar links, footer text, meta descriptions, etc. If something requires a more functional UI or deeper forms of manipulation, I'll build whatever custom admin UI I need.
Plus, I'm already in Workflowy 24x7 anyway, so it makes updating my site a breeze.
At least until Workflowy changes their internal API endpoints, which will break everything. :)
If anyone wants to know more I'd love to talk about it or share the code.
.02
I also tried to use it as a CMS. Using an 3rd party app in Google Drive for editing HTML files and then including it in my website, but i had problems with connecting the webapp with Google Drive OAUTH (spreadsheets was a no-brainer fyi). The problems were with a combo of Google Drive, OAuth and the .Net library that Google released (API V2. i suppose) :-(
I now use a file based database in Asp.Net MVC for my CMS. I'm updating it with every new website i have to create (if the client wants a CMS, off course).
I'm kinda curious what their backup method is when Google Drive goes down? (i thought about caching and a button for the client for cleaning the websites cache, so they could see their changes. )
Happy to give anyone an account if you'd like to beta test.
Also, Brace.io folks -- great stuff. we should chat :)
Welcoming the oncoming downvotes.
It's not really a static site once you have dynamic content on it.
So it does have its place but probably has a limited sweet spot. Is your end user already familiar with spreadsheets, possibly might want to view/edit the data in bulk, not going to pay you to build ur own editor over the data, not really that concerned about performance on a large scale? Then this might be a good solution for them.... Its basically MS Access in the cloud...
After reading your comment, I'm thinking that it may be easier in some situations like a teacher posting curriculum. It's also much easier than setting up a Wordpress deployment.