A JCR View of the World: Everything is Content
summary
Shows how Adobe CQ5 based on Apache Jackrabbit and Sling models content as nested nodes and properties and stores code, config and assets in one repository used by large sites like General Motors and McDonalds. Demonstrates concrete patterns: images as folders with renditions, micro-trees for page regions, print queue and workflow trees, replication from authoring to publish, and hot backups on append only files. Claims JCR trades web scale for rich features like JCR observation and content as trees that simplify versioning, access control and evolution.
AI-written summary · about
chapters (14)
- 0:00Introduction to JCR
- 1:52JCR as file system on steroids
- 3:59JCR vs NoSQL databases
- 4:43JCR Explorer demo
- 5:45Content structure examples
- 7:51Print queue workflow example
- 8:54Configuration as content
- 9:39Storing code in JCR
- 10:40Workflow modeling
- 12:25Asset ingestion patterns
- 13:30Access control in JCR
- 14:57Benefits of JCR structure
- 15:41Hierarchy in content systems
- 16:02Q&A on replication and backups
related talks
50mContent Before Code - A D8 Case Study
05mEverett Toews - Ignite OSCON 2014
27mContext First: A Unified Field Theory of Publishing
23mMaster JIRA APIs: Essential Documentation Tips
36mRefreshing the John Carter Brown Library’s Web Presence for Non-Academic Audiences
17mA case study: Ditching the paper for Drupal
10mShow, Don't Tell
43mC4 models as code