Fitting Plone in a custom stack
Upcoming SlideShare
Loading in...5
×
 

Fitting Plone in a custom stack

on

  • 862 views

 

Statistics

Views

Total Views
862
Views on SlideShare
862
Embed Views
0

Actions

Likes
1
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Fitting Plone in a custom stack Fitting Plone in a custom stack Presentation Transcript

  • fitting in a custom stack
  • Who am I ● Simone Deponti ● Python/Plone developer @ Abstract ● simone.deponti@abstract.it
  • The customer ● Largest on-line retailer in Italy ● Several brands View slide
  • The initial situation March of the Cart Catalog empire Marketing kingdom ...and a lot of small Imperial cities View slide
  • The problem ● Need to manage “marketing” content ● To integrate already existing content ● Stand alone
  • The problem (2) ● “Large theatre of operations” ● Must maintain good relations with “neighbouring states” ● Parallel universes (multisite)
  • What do we need? Speed Flexibility Coherence
  • I better clarify...
  • Speed ● No ● Repetitive tasks ● “useless” steps ● Yes ● One click one kill
  • Flexibility ● Marketing is not accounting ● Creatives ● Exception is routine ● Knowledged users ● Web is their work ● Possesses skills (that we can leverage)
  • Coherence ● Few base concepts ● Stick to them! ● Fast training
  • The solution ● “Aggregated” content ● “multicast” publication ● Information Architecture CMS != IA Site
  • The solution (2) ● Primary content ● Page is folder ● Object “composition” ● Templating (Genshi)
  • The solution (3) ● “primary” content ● Explicit positioning of root element ● Site-level multicast ● Internal structure follows Plone IA
  • The solution (4) ● Several content types ● “Standalone” or providing interfaces to internal WS ● Can be used within “primary” content
  • Lessons learned ● Plone's structure is optimal to manage content ● Presenting content is an altogether different story ● In the presentation layer, multiple is good, while managing, it's a <CENSORED>
  • Lessons learned ● Integration is simple if functional area are well defined and grouped ● Several ways: ● Webservice ● SQL ● Etc etc
  • Challenges ● Know the stack ● Automated refresh ● Componentize, componentize, componentize
  • And then? ● You can always do better ● Still too many useless steps ● Fine grained security ● UI polishing
  • Cast ● Plone ● Genshi ● SQLAlchemy ● PostgreSQL ● SOLR