it's the way of the present - why you should use plone.app.contenttypes

14
It‘s the way of the present Why you should use plone.app.contenttypes Philip Bauer

Upload: philip-bauer

Post on 14-Jan-2015

430 views

Category:

Technology


3 download

DESCRIPTION

A introduction to the state of plone.app.contenttypes. p.a.c replaces the default content-types in Plone with Dexterity-based types. Presented at the Plone Open Garden 2013 in Sorrento, Italy.

TRANSCRIPT

Page 1: It's the way of the present - Why you should use plone.app.contenttypes

It‘s the way of the present

Why you should use plone.app.contenttypes

Philip Bauer

Page 2: It's the way of the present - Why you should use plone.app.contenttypes

$ whoami

• Philip Bauer

• Location: Munich

• Education: Historian

• Choice: Web-Developer

• Plone: since version 2.1

• Founder of

Page 3: It's the way of the present - Why you should use plone.app.contenttypes

The way of the future

Deco

One content-type to rule them all

... or maybe two?

Page 4: It's the way of the present - Why you should use plone.app.contenttypes

WHERE IS IT?

Page 5: It's the way of the present - Why you should use plone.app.contenttypes

Meanwhile...

• I love Dexterity!

• It‘s lighter

• It‘s faster

• It‘s much better to develop with

• It‘s more powerfull, more pythonic and uses less boilerplate

• It has killer feature #1: ttw-schema-editor

• It has killer feature #2: behaviors

Page 6: It's the way of the present - Why you should use plone.app.contenttypes

plone.app.contenttypes

• Started during post-conference-sprint in San Francisco

• Limi said it will not be part of Plone

• In production for more than 1.5 years

Page 7: It's the way of the present - Why you should use plone.app.contenttypes

Features

• 1:1 replacement (almost)

• Works with a mixture of Archetypes and Dexterity

• Browser views (finally)

• Works with plone.app.multilingual (which also works with AT)

• TTW-editing of schemata

Page 8: It's the way of the present - Why you should use plone.app.contenttypes

Features II

• Better collections: merged from plone.app.collection 2.x

• Better events: plone.app.event (works in a branch)

• Better widgets: plone.app.widgets (works in a branch)

• This is the achievement of:- Timo Stollenwerk- Johannes Raggam- Rok Garbas- many others

Page 9: It's the way of the present - Why you should use plone.app.contenttypes

Demo

Page 10: It's the way of the present - Why you should use plone.app.contenttypes

Migration

• Old default types to plone.app.contenttypes

• (... except collections)

• If you don‘t want to migrate: Viewing AT-instances still works (but not editing)

• Needed: AT-Collections to DX-Collections (1.x -> 2.x)

• Needed: Old p.a.c.-event to plone.app.event

Page 11: It's the way of the present - Why you should use plone.app.contenttypes

The Future

• PLIP 2344 targets Plone 4.4

• Pre-installed (with upgrades) vs. installable addon

• DX or AT as default for new sites?

• We will see a lot of behaviors

Page 12: It's the way of the present - Why you should use plone.app.contenttypes

What you should do today and tomorrow

• Test and report bugs

• Improve and write migrations

• Improve and write tests

• Help get plone.app.widget ready and test them

• Test in Plone 4.0+

• Test documentation

• Add translations (e.g. leadimage-behavior)

• Improve templates (e.g. show references)

Page 13: It's the way of the present - Why you should use plone.app.contenttypes

What you should do next week

• Make sure your addons work with Dexterity and p.a.c

• I did TinyMCE and eea.facettednavigation you do the rest...