Part 2 of my response to Julian Wraith’s future of content management meme. This part looks at CMS architecture, rather than the technology choices of the first part, talking about application development and content repositories.
Categories: CMS
-
Unread links from Instapaper- Breadcrumbs - Webmaster Tools Help
- Infrequently asked questions on deterministic distributed transaction management | yang's blog
- To Trie or not to Trie – a comparison of efficient data structures
- If You Have To Tweet About Me Before I Give You Content, Will You Still Respect Me In The Morning? | Techdirt
- Introducing fise, the Open Source RESTful Semantic Engine, Nuxeo Developers Blog
- wkhtmltopdf - Project Hosting on Google Code
- Interactive Application Architecture Patterns
- Pricing models, the freemium myth and why you may not be charging enough for your product | Seth Levine
- expedient-desirable-product
- the-principle-of-one-degree
