Tweet
Tweet

Slide 1

Slide 1 text

? Yet another CMS Think twice about it

Slide 2

Slide 2 text

Stefano Verna @steffoz 2012 Ruby/ObjC developer at Cantiere Creativo 2010 Partner at weLaika http://stefanoverna.com

Slide 3

Slide 3 text

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.

Slide 4

Slide 4 text

“I’m working on a new CMS that...”

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

2.500 Open-source CMS projects ~

Slide 10

Slide 10 text

250 Commercial CMS products ~

Slide 11

Slide 11 text

0 Do it yourself CMS

Slide 12

Slide 12 text

15.000? Grand total (mostly in PHP)

Slide 13

Slide 13 text

15.000 unique solutions to a problem?

Slide 14

Slide 14 text

“I’m working on a new CMS that...”

Slide 15

Slide 15 text

Why?

Slide 16

Slide 16 text

1Vendor lock-in

Slide 17

Slide 17 text

Branding strategy 2

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

3 Inexperience

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

90% of complexity is here 90% is easy stuff

Slide 22

Slide 22 text

“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

Slide 23

Slide 23 text

{

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

http://railsyardcms.org

Slide 26

Slide 26 text

Refreshingly new!! pun intended

Slide 27

Slide 27 text

Ruby

Slide 28

Slide 28 text

3 years ago

Slide 29

Slide 29 text

3 complete rewrites

Slide 30

Slide 30 text

Railsyard 1 an (internal) experiment

Slide 31

Slide 31 text

Users Articles Pages Translations

Slide 32

Slide 32 text

Users Articles Pages Translations Users Articles Pages Translations

Slide 33

Slide 33 text

Users Articles Pages Translations Users Articles Pages Translations Users Articles Pages Translations

Slide 34

Slide 34 text

Users Articles Pages Translations Users Articles Pages Translations Users Articles Pages Translations

Slide 35

Slide 35 text

Railsyard 2 naïve open project

Slide 36

Slide 36 text

a couple of mentions and committers :(

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

Railsyard 3: a serious bet

Slide 39

Slide 39 text

Generalist CMS are complex

Slide 40

Slide 40 text

Clients need extreme simplicity

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

Cra a back-end experience that fits the clients mental model of how the website should be edited Deliver on time and within budget

Slide 44

Slide 44 text

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

Slide 45

Slide 45 text

Content Management System

Slide 46

Slide 46 text

Content Management Framework

Slide 47

Slide 47 text

Front-end is not your affair. This is what web frameworks are made for. Routing Controllers Views

Slide 48

Slide 48 text

Content to be managed is different 100% of the time. Don’t bother thinking about “standard usage cases”. They don’t exist.

Slide 49

Slide 49 text

CMS must have no interface by default?

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

Make it dead easy to build an “editing module” for each possibile type of content.

Slide 52

Slide 52 text

How?

Slide 53

Slide 53 text

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

Slide 54

Slide 54 text

A form is just a composition of basic editing fields: Text input Text area Checkbox Select/Dropdown File upload

Slide 55

Slide 55 text

Artist Artist Artist Artist Name Bio Country Homepage Text input Textarea Dropdown Text input

Slide 56

Slide 56 text

List resources

Slide 57

Slide 57 text

Railsyard.register  Artist  do    list  do        column  :title        column  :created_at    end end

Slide 58

Slide 58 text

Create/edit resource

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

Railsyard.register  Artist  do    form  do        field  :name        field  :bio        field  :country        field  :homepage_url    end end

Slide 61

Slide 61 text

90% of complexity 90% is easy stuff

Slide 62

Slide 62 text

No content

Slide 63

Slide 63 text

Version A Version B Remove res. Edit resources List resources

Slide 64

Slide 64 text

Plugins

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

Railsyard.register  Genre  do    list  do        as_tree        sortable        column  :name        column  :created_at    end end

Slide 67

Slide 67 text

Data-export Image galleries Search Translations Authentication Image resize Authorization

Slide 68

Slide 68 text

Resource relations Artist Award Award

Slide 69

Slide 69 text

Resource relations Artist Award Award

Slide 70

Slide 70 text

No content

Slide 71

Slide 71 text

Railsyard.register  Artist  do    form  do        #  previous  fields  here        has_many  :awards  do            field  :name            field  :year        end    end end

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

Railsyard.register  Artist  do    edit  do      field  :bio,  as:  :wysihtml5    end end

Slide 74

Slide 74 text

File uploads

Slide 75

Slide 75 text

field  :cover,  as:  :upload Upload field

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

has_one  :cover  do      field  :image,  as:  :upload      field  :alt,  :title end Upload field

Slide 78

Slide 78 text

has_one  :cover  do      field  :image,  as:  :upload      field  :alt,  :title end Upload field

Slide 79

Slide 79 text

image_metas  :cover

Slide 80

Slide 80 text

Do you still want to create a CMS? :)

Slide 81

Slide 81 text

Gain traction

Slide 82

Slide 82 text

Open-source marketing Let the community drive your effort

Slide 83

Slide 83 text

Minimize the perceived risk of the product Document everything

Slide 84

Slide 84 text

README Website Tutorial/Getting started Demo Support Tests ...

Slide 85

Slide 85 text

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.

Slide 86

Slide 86 text

thanks! Stefano Verna @steffoz (http://railsyardcms.org)