This is the deck from my talk at JoomlaDay Italia 2012 in Turin. If it is not clear by the slides alone, I'm trying to generate interest and volunteers to see this integrated into the core.
4. About me
• Joomla! and OSM founder, former OSM board member
• Active FOSS supporter: PHP, Joomla!, Lithium, MongoDB, PostgreSQL
5. About me
• Joomla! and OSM founder, former OSM board member
• Active FOSS supporter: PHP, Joomla!, Lithium, MongoDB, PostgreSQL
• Moved from NYC -> TO in May 2011
6. About me
• Joomla! and OSM founder, former OSM board member
• Active FOSS supporter: PHP, Joomla!, Lithium, MongoDB, PostgreSQL
• Moved from NYC -> TO in May 2011
• Yes, I’m a New Yorker, I talk fast. Sorry about that.
7. About me
• Joomla! and OSM founder, former OSM board member
• Active FOSS supporter: PHP, Joomla!, Lithium, MongoDB, PostgreSQL
• Moved from NYC -> TO in May 2011
• Yes, I’m a New Yorker, I talk fast. Sorry about that.
• CTO at Sounday Music: http://www.soundaymusic.com/
8. About me
• Joomla! and OSM founder, former OSM board member
• Active FOSS supporter: PHP, Joomla!, Lithium, MongoDB, PostgreSQL
• Moved from NYC -> TO in May 2011
• Yes, I’m a New Yorker, I talk fast. Sorry about that.
• CTO at Sounday Music: http://www.soundaymusic.com/
• Nuthin’ but startups. Period.
9. About me
• Joomla! and OSM founder, former OSM board member
• Active FOSS supporter: PHP, Joomla!, Lithium, MongoDB, PostgreSQL
• Moved from NYC -> TO in May 2011
• Yes, I’m a New Yorker, I talk fast. Sorry about that.
• CTO at Sounday Music: http://www.soundaymusic.com/
• Nuthin’ but startups. Period.
• Skate punk, hardcore bassist, american football coach, dad, husband
17. Current state of content
• If it is content, then it must live in com_content
18. Current state of content
• If it is content, then it must live in com_content
• That means it has to live in the jos_content table in the database
19. Current state of content
• If it is content, then it must live in com_content
• That means it has to live in the jos_content table in the database
• If it doesn’t fit, then it must not be content! Use a component and go
somewhere else:
20. Current state of content
• If it is content, then it must live in com_content
• That means it has to live in the jos_content table in the database
• If it doesn’t fit, then it must not be content! Use a component and go
somewhere else:
• Duplicate structure for new content metadata
21. Current state of content
• If it is content, then it must live in com_content
• That means it has to live in the jos_content table in the database
• If it doesn’t fit, then it must not be content! Use a component and go
somewhere else:
• Duplicate structure for new content metadata
• Duplicate plugins for search, etc.
22. Current state of content
• If it is content, then it must live in com_content
• That means it has to live in the jos_content table in the database
• If it doesn’t fit, then it must not be content! Use a component and go
somewhere else:
• Duplicate structure for new content metadata
• Duplicate plugins for search, etc.
• Duplicate effort for admin interface
31. What does UCM do to your data model?
• Main metadata still lives in jos_content
32. What does UCM do to your data model?
• Main metadata still lives in jos_content
• Additional data can go in a separate table
33. What does UCM do to your data model?
• Main metadata still lives in jos_content
• Additional data can go in a separate table
• Takes advantage of better database acess
34. What does UCM do to your data model?
• Main metadata still lives in jos_content
• Additional data can go in a separate table
• Takes advantage of better database acess
• Leverages JCache so objects can be transparently cached/persisted
35. What does UCM do to your data model?
• Main metadata still lives in jos_content
• Additional data can go in a separate table
• Takes advantage of better database acess
• Leverages JCache so objects can be transparently cached/persisted
• Introduces new methods for access controls
36. What does UCM do to your data model?
• Main metadata still lives in jos_content
• Additional data can go in a separate table
• Takes advantage of better database acess
• Leverages JCache so objects can be transparently cached/persisted
• Introduces new methods for access controls
• You can define new types of content without touching the core