Plone Foundation | @plone | https://plone.org
The New Plone.org
Built on Plone 6
Rikupekka Oksanen
Plone Conference 2021 Online
Plone Foundation | @plone | https://plone.org
Abstract
I will discuss Plone Communications and Marketing
Team’s plans to renew plone.org to Plone 6, the
latest and greatest of all Plone-releases.
This talk will contain a short history of plone.org, the
rise and fall of plone.com, and will give a glimpse to
a new future.
I will tell about the challenges with the current site
and the possibilities with the new Plone 6 one.
This is also a call to action, since we will need
people helping with migration, design, theming and
content work.
Practise what you preach and eat you own dogfood
- plone.org should be the pinnacle of what you'll get
with out-of-the-box Plone.
https://2021.ploneconf.org/schedule/the-new-plone-org-built-on-plone-6
Rikupekka Oksanen
marketing@plone.org
Plone Foundation | @plone | https://plone.org
Plone
Communications
and Marketing
Team
● Érico Andrei
● Fulvio Casali
● Norbert Marrale
● Rikupekka Oksanen
● Sally Kleinfeldt
● William Fennie
● And special thanks to
T. Kim Nguyen
https://plone.org/community/communications-and-marketing
Plone Foundation | @plone | https://plone.org
Some history of
plone.org
The first plone.org
was published in 2002
Plone Foundation | @plone | https://plone.org
Plone 1 in 2002
Plone Foundation | @plone | https://plone.org
Plone 1 in 2002
November
Plone Foundation | @plone | https://plone.org
Plone 2
in 2005
Plone Foundation | @plone | https://plone.org
Plone 3
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
Plone.net served
as a marketing
oriented site, with
case studies,
service providers
and media
coverage
Plone Foundation | @plone | https://plone.org
First Plone 4
based site 2009
Plone Foundation | @plone | https://plone.org
Plone 4.3
Plone Foundation | @plone | https://plone.org
The current
plone.org
Plone Foundation | @plone | https://plone.org
Built on Plone 5,
published in 2016
Oriented towards the
community and
developers
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
News archive - all
content migrated
through different
plone.org versions
Since 2002
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
19 years!
Now that’s content
management for
you!
Plone Foundation | @plone | https://plone.org
Plone.org
&
Plone.com
● An idea to separate marketing and
community sites
○ Like we did with plone.net
● Pros
○ Contains actual marketing material: case
studies, features, nice visual presentation
○ In the beginning plone.com also had
documentation, PLIPs etc. but since they
were moved
● Cons
○ Its was hard to manage plone.com content,
ironically
○ Updating two sites is two times the work
○ Creates confusion - should I use plone.com
or plone.org?
● Situation now: plone.com was removed
this September
Plone Foundation | @plone | https://plone.org
Plone.org
&
Plone.com
Plone Foundation | @plone | https://plone.org
Problems with
the current
plone.org
● Through-the-web editing partly
missing
○ → Hard to maintain some parts
● Some missing style elements
due to old customizations
● Diazo theme hard to develop
after a pause
● Does not represent Plone 6
and the 2020’s
Plone Foundation | @plone | https://plone.org
Suggestion:
renew plone.org
1. Showcase what Plone is today -
Plone 6
2. Make it easy to use, easy to update
3. Use own migration tools - we learn
and improve those
4. Eat your own dogfood - use Plone 6
It will push development forward
5. Visual overhaul - to this decade
6. Content management
Plone Foundation | @plone | https://plone.org
But can we do
all this?
Plone Foundation | @plone | https://plone.org
We could try 1. Make a rough plan
2. Aim for a certain timeframe
3. Build a new testing site with Plone 6
4. Do Migration (in-place or other?)
5. Create a design and images (icons,
banner and such)
6. Do content work (new main section
content)
7. Think of navigation
8. Test it on a preview site
9. Organize sprints (scheduled for
upcoming months)
10. Plan for version updates in sync
with Plone 6 versions
Plone Foundation | @plone | https://plone.org
Facelift and content
work 2020-2021
● Reorganized news and other
content, tagging
● Image improvements, cropping
● Theming improvements
● What is Plone -section and
Plone 6 info added
● Content and information
architecture figured out
● -> We know now what works on
the site and what especially
needs improving
Plone Foundation | @plone | https://plone.org
Planning
● Make a rough plan
● Aim for a certain timeframe
● How to migrate
● How to create a test site
● How to keep site up to date
with new Plone versions
● Publish and discuss the plan,
iterate
Let’s discuss!
Plone Foundation | @plone | https://plone.org
What to
highlight?
● What is Plone
● Plone (6) features
● How to get Plone
● Lovely community & how to
get involved
● News and events
● Documentation (linked)
● Foundation
● (teams, history)
● Something else?
Let’s discuss!
Plone Foundation | @plone | https://plone.org
Target
audiences
● Plone community
○ Current users and developers
● New potential users
○ End users
○ Integrator/decision maker
● New developers
○ From JS, Python world
● Other? Social media influencers?
Let’s discuss!
Plone Foundation | @plone | https://plone.org
The new
plone.org
Is Plone 6
Plone Foundation | @plone | https://plone.org
Plone 6
The features, stability, scalability, and
best-in-class security of an enterprise CMS,
combined with a modern, easy-to-use, and
powerful front end based on state-of-the art web
technologies.
Highlight and demonstrate this on plone.org
Plone 6 presentation - check out Timo
Stollenwerk’s Keynote
https://plone.org/what-is-plone/plone/plone-6/
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
Plone Foundation | @plone | https://plone.org
Plone.org should
be vanilla Plone 6
● Reduces need for special design
and theme customization
● Plone 6 already has lots of great
add-ons
● “Plone 6 does all this” - use
out-of-the-box features and
available add ons
● Stay true to what Plone 6 offers
● It has worked well before -
plone.org is Plone
Plone Foundation | @plone | https://plone.org
Plone.org 20 years ago
Plone Foundation | @plone | https://plone.org
What is plone
User feedback
Clear
navigation
News
Roadmap
Get Plone
Vanilla Plone
Plone Foundation | @plone | https://plone.org
Plone 6 today
Plone Foundation | @plone | https://plone.org
Design and
style
● Vanilla Plone 6, but with nice
content design
○ Huge banner image?
○ Pretty icons for features?
○ Nice CSS-effects, transitions?
○ What will frontpage hold?
We need
help with
design and
graphics
Plone Foundation | @plone | https://plone.org
Testing site
● We will need a staging/testing
site where we can play safely
and create new content
Help us
putting up a
new site!
Plone Foundation | @plone | https://plone.org
Migration
● Plone.org contains working
content since 2002
● We want to keep that as a living
testament to Plone’s ability as
a content management system
● Also a learning experience
We are looking
for help with
migration
Plone Foundation | @plone | https://plone.org
Content work
● Front page
● Main section pages using Volto
blocks
● Highlight Plone features and use
cases
● Going through migrated content
● We are looking for help with Plone
6 screencasts
● The kids today like videos
We are also
looking for help
with contents
Plone Foundation | @plone | https://plone.org
Sprints
● We will schedule upcoming
online sprints
● Monthly sprints, starting from
early December, then January
and so on
● Plone Conference sprint next
weekend!
Plone Foundation | @plone | https://plone.org
Summary ● Goal: To renew plone.org in 2022
● Using Plone 6 out-of-the-box
● Help wanted
Plone Foundation | @plone | https://plone.org
Call to action
● Discussion about the plan
● Discussion about Plone.org
contents and audiences
● Migration info/suggestions
● Putting up a testing site and CI
● Help with visuals and images
● Help with content work
● And more :)
Plone Foundation | @plone | https://plone.org
Next steps
Communication and marketing
team will provide
● Info page to sum up the vision
and plan
● Community post of the same
information
● Shared planning document
● Scheduled sprints
● Discussion channel with join
link
● Marketing team contact info
● Github issues list
● How to contribute -info
● Open Space discussion
https://plone.org/roadmap/
plone-org-renewal-2022
Plone Foundation | @plone | https://plone.org
Join the open
space discussion!
Let’s discuss about this on Friday
29th Open Spaces!
Plone Foundation | @plone | https://plone.org
Thank you!
https://2021.ploneconf.org/schedule/the-new-plone-org-built-on-plone-6
https://plone.org/roadmap/plone-org-renewal-2022
Plone Foundation | @plone | https://plone.org
/plone @plone
PloneCMS
plone.org

The New plone.org Built on Plone 6

  • 1.
    Plone Foundation |@plone | https://plone.org The New Plone.org Built on Plone 6 Rikupekka Oksanen Plone Conference 2021 Online
  • 2.
    Plone Foundation |@plone | https://plone.org Abstract I will discuss Plone Communications and Marketing Team’s plans to renew plone.org to Plone 6, the latest and greatest of all Plone-releases. This talk will contain a short history of plone.org, the rise and fall of plone.com, and will give a glimpse to a new future. I will tell about the challenges with the current site and the possibilities with the new Plone 6 one. This is also a call to action, since we will need people helping with migration, design, theming and content work. Practise what you preach and eat you own dogfood - plone.org should be the pinnacle of what you'll get with out-of-the-box Plone. https://2021.ploneconf.org/schedule/the-new-plone-org-built-on-plone-6 Rikupekka Oksanen [email protected]
  • 3.
    Plone Foundation |@plone | https://plone.org Plone Communications and Marketing Team ● Érico Andrei ● Fulvio Casali ● Norbert Marrale ● Rikupekka Oksanen ● Sally Kleinfeldt ● William Fennie ● And special thanks to T. Kim Nguyen https://plone.org/community/communications-and-marketing
  • 4.
    Plone Foundation |@plone | https://plone.org Some history of plone.org The first plone.org was published in 2002
  • 5.
    Plone Foundation |@plone | https://plone.org Plone 1 in 2002
  • 6.
    Plone Foundation |@plone | https://plone.org Plone 1 in 2002 November
  • 7.
    Plone Foundation |@plone | https://plone.org Plone 2 in 2005
  • 8.
    Plone Foundation |@plone | https://plone.org Plone 3
  • 9.
    Plone Foundation |@plone | https://plone.org
  • 10.
    Plone Foundation |@plone | https://plone.org
  • 11.
    Plone Foundation |@plone | https://plone.org Plone.net served as a marketing oriented site, with case studies, service providers and media coverage
  • 12.
    Plone Foundation |@plone | https://plone.org First Plone 4 based site 2009
  • 13.
    Plone Foundation |@plone | https://plone.org Plone 4.3
  • 14.
    Plone Foundation |@plone | https://plone.org The current plone.org
  • 15.
    Plone Foundation |@plone | https://plone.org Built on Plone 5, published in 2016 Oriented towards the community and developers
  • 16.
    Plone Foundation |@plone | https://plone.org
  • 17.
    Plone Foundation |@plone | https://plone.org
  • 18.
    Plone Foundation |@plone | https://plone.org
  • 19.
    Plone Foundation |@plone | https://plone.org
  • 20.
    Plone Foundation |@plone | https://plone.org News archive - all content migrated through different plone.org versions Since 2002
  • 21.
    Plone Foundation |@plone | https://plone.org
  • 22.
    Plone Foundation |@plone | https://plone.org 19 years! Now that’s content management for you!
  • 23.
    Plone Foundation |@plone | https://plone.org Plone.org & Plone.com ● An idea to separate marketing and community sites ○ Like we did with plone.net ● Pros ○ Contains actual marketing material: case studies, features, nice visual presentation ○ In the beginning plone.com also had documentation, PLIPs etc. but since they were moved ● Cons ○ Its was hard to manage plone.com content, ironically ○ Updating two sites is two times the work ○ Creates confusion - should I use plone.com or plone.org? ● Situation now: plone.com was removed this September
  • 24.
    Plone Foundation |@plone | https://plone.org Plone.org & Plone.com
  • 25.
    Plone Foundation |@plone | https://plone.org Problems with the current plone.org ● Through-the-web editing partly missing ○ → Hard to maintain some parts ● Some missing style elements due to old customizations ● Diazo theme hard to develop after a pause ● Does not represent Plone 6 and the 2020’s
  • 26.
    Plone Foundation |@plone | https://plone.org Suggestion: renew plone.org 1. Showcase what Plone is today - Plone 6 2. Make it easy to use, easy to update 3. Use own migration tools - we learn and improve those 4. Eat your own dogfood - use Plone 6 It will push development forward 5. Visual overhaul - to this decade 6. Content management
  • 27.
    Plone Foundation |@plone | https://plone.org But can we do all this?
  • 28.
    Plone Foundation |@plone | https://plone.org We could try 1. Make a rough plan 2. Aim for a certain timeframe 3. Build a new testing site with Plone 6 4. Do Migration (in-place or other?) 5. Create a design and images (icons, banner and such) 6. Do content work (new main section content) 7. Think of navigation 8. Test it on a preview site 9. Organize sprints (scheduled for upcoming months) 10. Plan for version updates in sync with Plone 6 versions
  • 29.
    Plone Foundation |@plone | https://plone.org Facelift and content work 2020-2021 ● Reorganized news and other content, tagging ● Image improvements, cropping ● Theming improvements ● What is Plone -section and Plone 6 info added ● Content and information architecture figured out ● -> We know now what works on the site and what especially needs improving
  • 30.
    Plone Foundation |@plone | https://plone.org Planning ● Make a rough plan ● Aim for a certain timeframe ● How to migrate ● How to create a test site ● How to keep site up to date with new Plone versions ● Publish and discuss the plan, iterate Let’s discuss!
  • 31.
    Plone Foundation |@plone | https://plone.org What to highlight? ● What is Plone ● Plone (6) features ● How to get Plone ● Lovely community & how to get involved ● News and events ● Documentation (linked) ● Foundation ● (teams, history) ● Something else? Let’s discuss!
  • 32.
    Plone Foundation |@plone | https://plone.org Target audiences ● Plone community ○ Current users and developers ● New potential users ○ End users ○ Integrator/decision maker ● New developers ○ From JS, Python world ● Other? Social media influencers? Let’s discuss!
  • 33.
    Plone Foundation |@plone | https://plone.org The new plone.org Is Plone 6
  • 34.
    Plone Foundation |@plone | https://plone.org Plone 6 The features, stability, scalability, and best-in-class security of an enterprise CMS, combined with a modern, easy-to-use, and powerful front end based on state-of-the art web technologies. Highlight and demonstrate this on plone.org Plone 6 presentation - check out Timo Stollenwerk’s Keynote https://plone.org/what-is-plone/plone/plone-6/
  • 35.
    Plone Foundation |@plone | https://plone.org
  • 36.
    Plone Foundation |@plone | https://plone.org
  • 37.
    Plone Foundation |@plone | https://plone.org Plone.org should be vanilla Plone 6 ● Reduces need for special design and theme customization ● Plone 6 already has lots of great add-ons ● “Plone 6 does all this” - use out-of-the-box features and available add ons ● Stay true to what Plone 6 offers ● It has worked well before - plone.org is Plone
  • 38.
    Plone Foundation |@plone | https://plone.org Plone.org 20 years ago
  • 39.
    Plone Foundation |@plone | https://plone.org What is plone User feedback Clear navigation News Roadmap Get Plone Vanilla Plone
  • 40.
    Plone Foundation |@plone | https://plone.org Plone 6 today
  • 41.
    Plone Foundation |@plone | https://plone.org Design and style ● Vanilla Plone 6, but with nice content design ○ Huge banner image? ○ Pretty icons for features? ○ Nice CSS-effects, transitions? ○ What will frontpage hold? We need help with design and graphics
  • 42.
    Plone Foundation |@plone | https://plone.org Testing site ● We will need a staging/testing site where we can play safely and create new content Help us putting up a new site!
  • 43.
    Plone Foundation |@plone | https://plone.org Migration ● Plone.org contains working content since 2002 ● We want to keep that as a living testament to Plone’s ability as a content management system ● Also a learning experience We are looking for help with migration
  • 44.
    Plone Foundation |@plone | https://plone.org Content work ● Front page ● Main section pages using Volto blocks ● Highlight Plone features and use cases ● Going through migrated content ● We are looking for help with Plone 6 screencasts ● The kids today like videos We are also looking for help with contents
  • 45.
    Plone Foundation |@plone | https://plone.org Sprints ● We will schedule upcoming online sprints ● Monthly sprints, starting from early December, then January and so on ● Plone Conference sprint next weekend!
  • 46.
    Plone Foundation |@plone | https://plone.org Summary ● Goal: To renew plone.org in 2022 ● Using Plone 6 out-of-the-box ● Help wanted
  • 47.
    Plone Foundation |@plone | https://plone.org Call to action ● Discussion about the plan ● Discussion about Plone.org contents and audiences ● Migration info/suggestions ● Putting up a testing site and CI ● Help with visuals and images ● Help with content work ● And more :)
  • 48.
    Plone Foundation |@plone | https://plone.org Next steps Communication and marketing team will provide ● Info page to sum up the vision and plan ● Community post of the same information ● Shared planning document ● Scheduled sprints ● Discussion channel with join link ● Marketing team contact info ● Github issues list ● How to contribute -info ● Open Space discussion https://plone.org/roadmap/ plone-org-renewal-2022
  • 49.
    Plone Foundation |@plone | https://plone.org Join the open space discussion! Let’s discuss about this on Friday 29th Open Spaces!
  • 50.
    Plone Foundation |@plone | https://plone.org Thank you! https://2021.ploneconf.org/schedule/the-new-plone-org-built-on-plone-6 https://plone.org/roadmap/plone-org-renewal-2022
  • 51.
    Plone Foundation |@plone | https://plone.org /plone @plone PloneCMS plone.org