Yet another CMS? Think twice about it.

Transcript

1. ? Yet another CMS Think twice about it
2. Stefano Verna @steffoz 2012 Ruby/ObjC developer at Cantiere Creativo 2010 Partner at weLaika http://stefanoverna.com
3. Content management system (CMS) • 1 (noun) a software application used to upload, edit, and manage content displayed on a website. A CMS can perform a variety of different tasks for a website, enabling less technical individuals to manage content on a website easily without having an extensive coding background.
4. “I’m working on a new CMS that...”
6. 10 20 30 40 50 60 Wordpress Joomla Drupal vBulletin Typo3 PHP Link Others 22.2 1.9 2.0 3.7 7.0 8.9 54.3 Alexa’s top million sites CMS usage
7. 10 20 30 40 50 60 Wordpress Joomla Drupal vBulletin Typo3 PHP Link Others 22.2 1.9 2.0 3.7 7.0 8.9 54.3 Alexa’s top million sites CMS usage
8. 10 20 30 40 50 60 Wordpress Joomla Drupal vBulletin Typo3 PHP Link Others 22.2 1.9 2.0 3.7 7.0 8.9 54.3 Alexa’s top million sites CMS usage
9. 2.500 Open-source CMS projects ~
10. 250 Commercial CMS products ~
11. 0 Do it yourself CMS
12. 15.000? Grand total (mostly in PHP)
13. 15.000 unique solutions to a problem?
14. “I’m working on a new CMS that...”
15. Why?
16. 1Vendor lock-in
17. Branding strategy 2
19. 3 Inexperience
21. 90% of complexity is here 90% is easy stuff
22. “When you throw away code and start from scratch, you are throwing away all that knowledge. All those collected bug fixes. Years of programming work.” Joel Spolsky
23. {
25. http://railsyardcms.org
26. Refreshingly new!! pun intended
27. Ruby
28. 3 years ago
29. 3 complete rewrites
30. Railsyard 1 an (internal) experiment
31. Users Articles Pages Translations
32. Users Articles Pages Translations Users Articles Pages Translations
33. Users Articles Pages Translations Users Articles Pages Translations Users Articles Pages Translations
34. Users Articles Pages Translations Users Articles Pages Translations Users Articles Pages Translations
35. Railsyard 2 naïve open project
36. a couple of mentions and committers :(
38. Railsyard 3: a serious bet
39. Generalist CMS are complex
40. Clients need extreme simplicity
43. Cra a back-end experience that fits the clients mental model of how the website should be edited Deliver on time and within budget
44. Cra a back-end experience that fits the clients mental model of how the website should be edited Deliver on time and within budget and
45. Content Management System
46. Content Management Framework
47. Front-end is not your affair. This is what web frameworks are made for. Routing Controllers Views
48. Content to be managed is different 100% of the time. Don’t bother thinking about “standard usage cases”. They don’t exist.
49. CMS must have no interface by default?
51. Make it dead easy to build an “editing module” for each possibile type of content.
52. How?
53. For each type of content: Create a DB table Listing of existing resources Creation of new resource Editing of existing resource Removal of existing resource
54. A form is just a composition of basic editing fields: Text input Text area Checkbox Select/Dropdown File upload
55. Artist Artist Artist Artist Name Bio Country Homepage Text input Textarea Dropdown Text input
56. List resources
57. Railsyard.register  Artist  do    list  do        column  :title        column  :created_at    end end
58. Create/edit resource
60. Railsyard.register  Artist  do    form  do        field  :name        field  :bio        field  :country        field  :homepage_url    end end
61. 90% of complexity 90% is easy stuff
63. Version A Version B Remove res. Edit resources List resources
64. Plugins
66. Railsyard.register  Genre  do    list  do        as_tree        sortable        column  :name        column  :created_at    end end
67. Data-export Image galleries Search Translations Authentication Image resize Authorization
68. Resource relations Artist Award Award
69. Resource relations Artist Award Award
71. Railsyard.register  Artist  do    form  do        #  previous  fields  here        has_many  :awards  do            field  :name            field  :year        end    end end
73. Railsyard.register  Artist  do    edit  do      field  :bio,  as:  :wysihtml5    end end
74. File uploads
75. field  :cover,  as:  :upload Upload field
77. has_one  :cover  do      field  :image,  as:  :upload      field  :alt,  :title end Upload field
78. has_one  :cover  do      field  :image,  as:  :upload      field  :alt,  :title end Upload field
79. image_metas  :cover
80. Do you still want to create a CMS? :)
81. Gain traction
82. Open-source marketing Let the community drive your effort
83. Minimize the perceived risk of the product Document everything
84. README Website Tutorial/Getting started Demo Support Tests ...
85. Recap. Think twice about creating a new CMS (open-source project) yourself; Classic CMS is not meant for web- agencies; CMF is a promising solution to the need of tailored backend UIs; Don’t forget what matters to the community.
86. thanks! Stefano Verna @steffoz (http://railsyardcms.org)