Presentation from phpday2011. La modellazione e gestione dei contenuti costituisce un dominio complesso. Soluzioni standard come Drupal, Joomla o Wordpress si adattano con difficoltà sul dominio di uno specifico cliente; d’altro canto soluzioni fatte in casa costano in termini di tempi di sviluppo e riusabilità. Non esiste allora "one cms to rule them all"? Nel talk verrà introdotto il progetto Symfony CMF discutendo tra l’altro di: - standard per la modellazione dei contenuti - modellazione ed organizzazione dei contenuti - scelte architetturali - linee guida per l’utlizzo del cmf

1. Symfony CMF
un nuovo paradigma per la gestione dei contenuti

2. Symfony CMF
buon
un nuovo paradigma per la gestione dei contenuti

3. Symfony CMF
buon
un nuovo paradigma per la gestione dei contenuti
approccio

4. ?
http://phpday.it #phpday

5. CMS are awesome!
http://phpday.it #phpday

6. No REALLY!
CMSes are awesome!
http://phpday.it #phpday

7. CMSes are awesome if
you are an end user!
Click click
http://phpday.it #phpday

8. CMSes are awesome if
you are a sales guy!
Brand
http://phpday.it #phpday

9. CMSes sucks if you are a
developer!
CMS first, framework second
http://phpday.it #phpday

10. CMSes nightmares
• no clean separation of configuration, logic and content
• no clean deployment and staging concept
• inconsistent cache layers
• lots of legacy baggage
• NIH (not invented here) syndrom
http://phpday.it #phpday

11. Do we also suffer from
NIH?
• Based ourselves as much on standard tools and specs
• Deliver value within a reasonable time
http://phpday.it #phpday

12. CMF = Content
Management Framework
• In other words: its a toolbox to create your
own custom CMS
• Not a one size fits all, but increase code
sharing
• Imagine Diem, Sympal, Apostrophe all build
on the same content foundation
http://phpday.it #phpday

13. Mission
• The Symfony CMF project makes it easier
for developers to add CMS functionality to
applications built with the Symfony2 PHP
framework. Key development principles for
the provided set of bundles are scalability,
usability, documentation and testing
http://phpday.it #phpday

14. Contents
http://phpday.it #phpday

15. Contents
http://phpday.it #phpday

16. i18n
http://phpday.it #phpday

17. Versioning
http://phpday.it #phpday

18. Relational DB
http://phpday.it #phpday

19. Architecture
content repository | Jackrabbit
http://phpday.it #phpday

20. Content Repository
• A content repository is a generic
application data “super store.”
• Can handle both small and large-scale data
interactions
• Is expected to manipulate and store
structured and unstructured content that
vary dynamically
http://phpday.it #phpday

21. JSR170 aka JCR1
JSR283 aka JCR2
• how data are stored within the repository
is identified and structured from the point
of view of the client
http://phpday.it #phpday

22. Workspaces
• Multiple workspaces, each with its own
name and root node
• Is similar to a Unix file system structure
• Each workspace is independent
http://phpday.it #phpday

23. Nodes
• Are identified by the path where are stored
• ex. id: “/my/path/under/water/fish”
• Can be created, deleted, modified, copied...
http://phpday.it #phpday

24. Properties
• Typed attribute:
• STRING, URI, BOOLEAN, LONG, DOUBLE,
DECIMAL, BINARY, DATE, NAME, PATH,
WEAKREFERENCE REFERENCE
• jcr:created, jcr:mimeType
http://phpday.it #phpday

25. Nodes
• Are typed using namespaced names
• nt:file, nt:folder...
• nt:unstructured
http://phpday.it #phpday

26. Node Mixins
• A mixin node type can be assigned to a
node during that node's lifetime
• mix:referenceable
• jcr:uuid
http://phpday.it #phpday

27. Node Mixins
• mix:versionable
• jcr:versionHistory
• jcr:predecessors
• jcr:baseVersion
• jcr:isCheckedOut
• jcr:mergeFailed
http://phpday.it #phpday

28. Content repository
Java implementation
http://phpday.it #phpday

29. Architecture
phpcr | Jackalope
content repository | Jackrabbit
http://phpday.it #phpday

30. PHPCR
• Aims to provide a standard API that can be
used by any PHP content management system
to interface with any content repository.
• Several Implementations
• Jackalope on Jackrabbit
• Jackalope on Doctrine DBAL
• Midgard2 PHPCR
http://phpday.it #phpday

31. PHPCR
• PHPCR has been submitted to JCR
• http://phpcr.github.com/
http://phpday.it #phpday

32. http://phpday.it #phpday

33. Architecture
doctrine | phpcr-odm
phpcr | Jackalope
content repository | Jackrabbit
http://phpday.it #phpday

34. PHPCR-ODM
• Sits on top of jackalope
• Works like MongoDB or CouchDB ODM,
but also includes a tree/graph, versioning
and ACL API
http://phpday.it #phpday

35. PHPCR-ODM
http://phpday.it #phpday

36. Document Class
http://phpday.it #phpday

37. Repository Class
http://phpday.it #phpday

38. CRUD
http://phpday.it #phpday

39. Traversal
http://phpday.it #phpday

40. Versioning
http://phpday.it #phpday

41. Not all data fits well in
PHPCR/JCR
• For example aggregation is better done in an
RDBMS
• Store web store product description in PHPCR/
JCR
• Store web store inventory and orders in RDBMS
http://phpday.it #phpday

42. Architecture
Sf2 | doctrinePHPCRBundle
doctrine | phpcr-odm
phpcr | Jackalope
content repository | Jackrabbit
http://phpday.it #phpday

43. DoctrinePHPCRBundle
• Document Manager available in the DIC
http://phpday.it #phpday

44. DEMO
http://phpday.it #phpday

45. Roadmap
• PHPCR-ODM: @Child, @Children, @Parent,
@ReferenceOne, @ReferenceMany, ...
• Make AdminBundle compatible
• Create frontend Bundles
http://phpday.it #phpday

46. Eating your own dog food
• Ideato is rebuilding its site on top of CMF
http://phpday.it #phpday

47. Many companies are
committed to the effort
http://phpday.it #phpday

48. Symfony CMF Camp
Cesena, 29-30 of July
http://www.unsito.com/c4
http://phpday.it #phpday

49. Resources
• irc://freenode/#symfony-cmf
• http://cmf.symfony.com/
• https://github.com/symfony-cmf/symfony-cmf/wiki
• http://jcp.org/en/jsr/detail?id=283
• http://jcp.org/en/jsr/detail?id=333
http://phpday.it #phpday

50. Thanks!
http://joind.in/3023
Michele Orselli Manuel Baldassarri
mo@ideato.it mb@ideato.it
http://phpday.it #phpday