Forgot your password?
New user?
Document Actions
#230: Update "Welcome to Plone" Page & Experience
- Contents
Plone's current "welcome-to-Plone" page provides links for help, etc., however, it needs redesign for attractiveness and effectiveness. In addition, two pieces of sample content (a news item and an event) should be created so the existing Collections are more obvious.
- Proposed by
- Joel Burton
- Seconded by
- Alexander Limi
- Proposal type
- User interface
- Assigned to release
- State
- being-discussed
Definitions
Motivation
- Despite being on the current "Welcome to Plone" page, many new users miss the links for Plone books, IRC support, and end-user manual.
- Due to Plone not showing navigation until level 2, there is no navigation in out-of-the-box Plone (there is no area where the nav is shown, given that none of the pre-created folders have any content that would appear in nav). This obscures the fact that we have nav as a feature from casual evaluators.
- We have no examples of using images in Plone content, a common area of misunderstanding for casual evaluators.
Assumptions
Proposal
- Update the existing front-page ("Welcome to Plone") page to remove the how-to-get help information. This will make it much smaller.
- Create a new top-level folder, getting-started ("Getting Started"). This will contain:
- a default document with similar information as the current home page, but more visually presented, published
- an image for Plone Chat (taken from plone.org's support page), published
- the image of "Plone books" (take form plone.org's support page), published
- a sample, very minimal news item, published
- a sample, very minimal event, published
Implementation
Deliverables
- A .zexp of the proposed new example folder and front-page will be created and discussed. This can be added to any site for testing purposed.
- Once approved, this content will be placed in the standard Plone GenericSetup profile.
- If Python code is required to install this, appropriate unit tests will need to be written
- Translation/localization of this is not required for success of this project; however, the translation teams may choose to translate this new content.
- No new documented is expected.
Risks
- This will ship content that most people will want to delete when they begin their "real" Plone site
- This is similar to the "News" and "Events" folders, which people delete before starting the real sites
- All of these will be in folder, so that ongoing improvements to the examples folder will not require to change their behavior
- The new welcome page may require translation
- The new event and news item may require translation
- However, given that we expect these to be very, very minimal, this translation shouldn't be too onerous
- This new content will use a bit of space in the ZODB
- The expected total difference of installer & ZODB size is less than 100k.
Progress log
- Discussed and PLIPed at the Strategic Planning Followup in New Orleans (6 Jun 2008)
Participants
- Joel Burton
- Alexander Limi
- Veda Williams
- Sam Knox (proposed, for helping with design/content of the new "welcome" page)
Agree with Wichert
Posted by
Ben Mason
at
September 28, 2008 - 12:32
I agree with Wichert. Whenever we start a new Plone project we have to remove the default content.
Having an 'install example content' option would be great.
Having an 'install example content' option would be great.
-1 on the implementation, +0.5 on the idea
Posted by
Hanno Schlichting
at
August 3, 2008 - 07:42
I agree with Wichert here, that this should not be in the default installation.
Rather I'd like to move all content including portlet assignments into a separate profile, which you can optionally choose to install while creating a new Plone site. I think an extra package called 'plone.app.demo' could work here.
Another note: We have gone through all the trouble of translating all the default content in Plone for Plone 3.0. Stepping back from that and only translating part of the content is not an option for me.
Technical note: Providing a zexp is not a good idea, as you cannot easily maintain it and change its content. It's also a nightmare to extract all the content from it in order to generate the translation files from it. Since we don't have any decent content import feature, I think hard-coding all this in Python code is the only viable option right now.
Rather I'd like to move all content including portlet assignments into a separate profile, which you can optionally choose to install while creating a new Plone site. I think an extra package called 'plone.app.demo' could work here.
Another note: We have gone through all the trouble of translating all the default content in Plone for Plone 3.0. Stepping back from that and only translating part of the content is not an option for me.
Technical note: Providing a zexp is not a good idea, as you cannot easily maintain it and change its content. It's also a nightmare to extract all the content from it in order to generate the translation files from it. Since we don't have any decent content import feature, I think hard-coding all this in Python code is the only viable option right now.
Visualising this improvement
Posted by
Graham Perrin
at
November 18, 2008 - 13:06
I suspect that if we add, to the words of this PLIP, one or two exemplary graphics (from what I have seen, 'less is more' and it's extremely attractive) -- and some context -- then more positive votes may be realised.
-1, -10 for doing this in CMFPlone
I am in favour of having an optional 'install example content' option during site creation. This could just install a new package which sets up the example content. This can be developed and maintained out-of-tree and offered for inclusion using the normal rules. CMFPlone is too complex already!