Fitting Plone in a custom stack
-
Upload
simone-deponti -
Category
Technology
-
view
820 -
download
1
Transcript of Fitting Plone in a custom stack
![Page 1: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/1.jpg)
fitting
in a custom stack
![Page 3: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/3.jpg)
The customerThe customer
● Largest on-line retailer in Italy● Several brands
![Page 4: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/4.jpg)
The initial situationThe initial situation
Catalog empire
March of the Cart
Marketing kingdom
...and a lot of small Imperial cities
![Page 5: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/5.jpg)
The problemThe problem
● Need to manage “marketing” content● To integrate already existing content● Stand alone
![Page 6: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/6.jpg)
The problem (2)The problem (2)
● “Large theatre of operations”● Must maintain good relations with
“neighbouring states”● Parallel universes (multisite)
![Page 7: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/7.jpg)
What do we need?What do we need?
Speed
Flexibility
Coherence
![Page 8: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/8.jpg)
I better clarify...
![Page 9: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/9.jpg)
SpeedSpeed
● No● Repetitive tasks● “useless” steps
● Yes● One click one kill
![Page 10: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/10.jpg)
FlexibilityFlexibility
● Marketing is not accounting● Creatives● Exception is routine
● Knowledged users● Web is their work● Possesses skills (that we can leverage)
![Page 11: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/11.jpg)
CoherenceCoherence
● Few base concepts● Stick to them!● Fast training
![Page 12: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/12.jpg)
The solutionThe solution
● “Aggregated” content● “multicast” publication● Information Architecture CMS != IA Site
![Page 13: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/13.jpg)
The solution (2)The solution (2)
● Primary content● Page is folder● Object “composition”● Templating (Genshi)
![Page 14: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/14.jpg)
The solution (3)The solution (3)
● “primary” content● Explicit positioning of root element● Site-level multicast● Internal structure follows Plone IA
![Page 15: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/15.jpg)
The solution (4)The solution (4)
● Several content types● “Standalone” or providing interfaces
to internal WS● Can be used within “primary” content
![Page 16: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/16.jpg)
Lessons learnedLessons 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>
![Page 17: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/17.jpg)
Lessons learnedLessons learned
● Integration is simple if functional area are well defined and grouped
● Several ways:● Webservice● SQL● Etc etc
![Page 18: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/18.jpg)
ChallengesChallenges
● Know the stack● Automated refresh● Componentize, componentize, componentize
![Page 19: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/19.jpg)
And then?And then?
● You can always do better● Still too many useless steps● Fine grained security● UI polishing
![Page 20: Fitting Plone in a custom stack](https://reader034.fdocuments.in/reader034/viewer/2022052522/554f77bfb4c9052a518b4848/html5/thumbnails/20.jpg)
CastCast
● Plone● Genshi● SQLAlchemy● PostgreSQL● SOLR