I've done something a bit similar on Lump.co, but I'm using Workflowy as a CMS there instead of Google Docs.
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.
Comments
I've done something a bit similar on Lump.co, but I'm using Workflowy as a CMS there instead of Google Docs.
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.