Actions

Difference between revisions of "Unified Content Model Working Group"

From Joomla! Documentation

(Roadmap)
(Roadmap)
(One intermediate revision by one user not shown)
Line 41: Line 41:
  
 
==Roadmap==
 
==Roadmap==
Initial infrastructure for use of a single core table: 3.1.
+
This effort can be thought of as two coordinated efforts:
Migration to a single core content table for all core components for 3.2
+
* Work on the CMS 3 series to implement UCM for the core and extensions that wish to opt into it.
 +
* Work on a the CMS 4 series that would be built around this model as well as other architectural changes.
 +
 
 +
Steps
 +
*Initial infrastructure for use of a single core table: 3.1.
 +
*Migration to a the single core content table for all or most core components for 3.2
  
 
==Meetings==
 
==Meetings==

Revision as of 00:04, 20 May 2013

The Unified Content Model Working Group is a Production Working Group. UCM is powerful new tool that is proposed for inclusion in the Platform. What use will the CMS make of it, what are the backward compatibility issues involved, what new coding would be needed to use it in the CMS, and what are the implications for third party extensions are all open questions.

Contents

Coordinators & PLT Contact

Elin Waring

Announcements

External resources

Background Materials

The original code from eBay

The first extended discussion on the platform mailing list.

Rob Schley talk at Joomla Day New York

Elin Waring slides for PWG lightning talks at Joomla and Beyond 2012

Video of PWG Meeting at JAB 2012

Video of session on UCM at Joomla World Conference

Slides from Elin's session on UCM at JWC

Sam's example of a web services application

Stefan's GSOC application using UCM

Deliverables

Long term, a new Joomla application for the management of content.

Technical Work produced by this group

Communications

Roadmap

This effort can be thought of as two coordinated efforts:

  • Work on the CMS 3 series to implement UCM for the core and extensions that wish to opt into it.
  • Work on a the CMS 4 series that would be built around this model as well as other architectural changes.

Steps

  • Initial infrastructure for use of a single core table: 3.1.
  • Migration to a the single core content table for all or most core components for 3.2

Meetings