Hippo GetTogether 2013-06-21 1040 Roadmap Generalized Repository Content API - Ate Douma Hippo

Ate Doume, Hippo Chief Architect details the plans Hippo has for a Generalized Repository Content API

Transcript

1. follow the Hippo trail 1 Create Digital Miracles follow the Hippo trail 1 HGT 2013 Hippo Roadmap Generalized Repository Content API Hippo GetTogether 2013
2. follow the Hippo trail 2 Create Digital Miracles follow the Hippo trail 2 HGT 2013 A new ContentType Model service • A dynamic ContentType Model service providing effective type definitions for: – the base JCR node types – the enhanced Hippo Document Types (hippo:namespaces) – any specific JCR node, including possible applied mixin types • Always 'up-to-date' against the current JCR node types and 'published' Hippo Document Types definitions • A public, stable and supported model service which: – hides the 'internal' hippo:namespaces configuration – hides effective JCR type model quirkiness – can be used to check and enforce a 'strict' Document Type model while using 'relaxed' JCR type definitions • Available: Hippo CMS 7.9 (already in trunk)
3. follow the Hippo trail 3 Create Digital Miracles follow the Hippo trail 3 HGT 2013 Generalized Repository Content API • A generic and dynamic Content model and CRUD management API wired by the ContentType model service: – like a JCR Node API on steroids – can be used to (automatically) enforce an enhanced and 'strict' Document type model while using 'relaxed' JCR type definitions – always 'up-to-date': published model changes are reflected immediately in the API, across all cluster nodes; no need for recompilation and deployment of manual generated code – handles all JCR node types and mixins for any effective JCR node (imagine coding or generating beans for every possible runtime combination...) – aligns with higher-end goals like zero-development / zero-redeploy – feasible for use-cases like a (new) declaritive workflow engine, import/export, replication, content packaging, auto REST services, generic/reusable HST components, …, etc.
4. follow the Hippo trail 4 Create Digital Miracles follow the Hippo trail 4 HGT 2013 Roadmap • initial effort: focus on generic / back-end use-cases like replication, new workflow engine, auto REST service, etc. • at a later stage: integration with HST Components and enhancing or replacing HST ContentBeans: – custom and derived properties, children and functions – dynamic language based HST Components (likely Groovy) – dynamic language based type-safe Content model beans – stored in and configured through the Hippo Repository – IDE / development tooling support, like with auto-export
5. follow the Hippo trail 5 Create Digital Miracles follow the Hippo trail 5 HGT 2013 Question & Answers Thank you so much for your time. Let’s stay in touch. www.onehippo.com +31 (0)20 522 44 66 or +1 877 414 4776