-
Hi: I think there is too much text in some pages. Main pages are entry points I think they should not be overloaded with contents. As an example the Community page currently wants to list everything linearly, mailing lists, IRC, local lists, local user groups, conferences, etc. This is too much and I've created a few subpages: "Mailing Lists", "IRC Channels", "Sprints", "Conferences" and there should probably be a few others. I have also added a folder "In your country", and there should be one page for each country, each one can give informations on the local lists and user groups. I've not yet moved the content As a second example, the Project page text is too long. The text itself is ok, but I believe it should be moved to subpages such as "History" or "Why zope" or something. The entry page should only contain a very short introduction, with links to the subprojects, and one only sentence that says "Zope has a long history. Over a decade! Learn more (link-> History Page)". There are interesting keywords (decade, mature, flexible, etc.) that must appear on the entry pages and we should build very short sentences made with these keywords. I personally find the Zope3 page extremely frightening, it currently begins with: "It is nearly impossible to come up with an all-encompassing definition of what "Zope 3" really is.". => My first thought: "Ok, they don't know themselves what they did, I don't go further, this is not for me". Again, we should list all the relevant keywords that represent Zope3, and build a few short and positive sentences with these words. That's all. Long text must be moved to subpages for people interested in reading further. Now a question: which old sites will be kept? Should we have to copy the tarball release into the Plone site? Christophe
-
Christophe Combelles a écrit : > Again, we should list all the relevant keywords that represent Zope3, > and build a few short and positive sentences with these words. That's > all. Long text must be moved to subpages for people interested in > reading further. I've begun to build a list of relevant keywords for each project. I think this can help building short sentences with all the notions. Do you have more? (or some to remove?). Zope the overall project: ------------------------- • decade • supported • flexible • powerful • open-source • free • python • object oriented • ...? Zope2 ----- • through-the-web development • easy to start • legacy • product • extensible • ...? Zope3 ----- • component architecture • module • flexible • library • application server • wsgi • object oriented • design-pattern • adapter • interface • object database • extensible • powerful • configuration • convention (->grok) • ...? ZODB ------ • transaction • persistence • savepoints • history • undo • blob • scalable • pluggable storage • ...?
-
I think there should be a common presentation pattern for the project pages, with the same subtitles and topics: 1) What is <project_name>? A short paragraph containing all the keywords previously listed. 2) History: a really short paragraph - for zope2: started in the 90's, was revolutionary, is still widely used and supported, etc... Plus a link to a separate long history page explaining principia, bobo, the opensourcing date,... - for zope3: rewritting begun in which year, first version zope X3 in which year, then several versions followed. Plus a link to a longer history page. 3) Download / Install <project_name> a really small download paragraph explaining that : for zope2: - there is a stable and a dev release, - the latest one is currently 2.x.x, with the date - z2 is an monolithic application that can be extended with products - a link to the page with all releases - a link to a new "Installation" subpage giving detailed installation instructions for zope3: - there is a stable and a dev release, - the latest one is currently 3.x, with the date - z3 must be downloaded and installed via pypi/buildout/zopeproject/kgs - there is a tarball release v3.x.x - a link to the page with all the releases, the date, - a link to the kgs versions.cfg - a link to a new "Installation" subpage giving detailed installation instructions (zopeproject) 4) Documentation a single sentence (with some keywords, tutorial, howtos, api, ...) that lead to the Documentation page. Christophe-
Christophe Combelles wrote: > I think there should be a common presentation pattern for the project pages, > with the same subtitles and topics: > > > 1) What is <project_name>? > A short paragraph containing all the keywords previously listed. > > 2) History: > a really short paragraph > - for zope2: started in the 90's, was revolutionary, is still widely used and > supported, etc... Plus a link to a separate long history page explaining > principia, bobo, the opensourcing date,... > > - for zope3: rewritting begun in which year, first version zope X3 in which > year, then several versions followed. Plus a link to a longer history page. > > 3) Download / Install <project_name> > a really small download paragraph explaining that : > for zope2: - there is a stable and a dev release, > - the latest one is currently 2.x.x, with the date > - z2 is an monolithic application that can > be extended with products > - a link to the page with all releases > - a link to a new "Installation" subpage giving > detailed installation instructions > > for zope3: - there is a stable and a dev release, > - the latest one is currently 3.x, with the date > - z3 must be downloaded and installed via > pypi/buildout/zopeproject/kgs > - there is a tarball release v3.x.x > - a link to the page with all the releases, the date, > - a link to the kgs versions.cfg > - a link to a new "Installation" subpage giving > detailed installation instructions (zopeproject) > > 4) Documentation > a single sentence (with some keywords, tutorial, howtos, api, ...) that lead to > the Documentation page. +1 to all of this Thanks for taking so much time to think through this, Chrisotphe! Unless you are worried that something is too controversial, feel free to just make changes. Better to ask forgiveness than permission sometimes. Just try to make sure you don't lose content that people have been working on that may not be finished yet.. Martin
-
Am 26.04.2008 um 12:26 schrieb Christophe Combelles: > I think there should be a common presentation pattern for the > project pages, with the same subtitles and topics: > > > 1) What is <project_name>? > A short paragraph containing all the keywords previously listed. > > 2) History: > a really short paragraph Yes, very very short. Yesterday is gone. Mit freundlichen Grüßen Jan Ulrich Hasecke -- DZUG e.V. - Deutschsprachige Zope User Group - www.zope.de - www.dzug.org Forster Straße 29 - 06112 Halle/Saale Telefon +49 345 122 9889 9 - Fax +49 345 122 9889 1
-
-
Christophe Combelles wrote: > Hi: > > I think there is too much text in some pages. Main pages are entry points I > think they should not be overloaded with contents. Agree. We can always create sub-objects. We can also use static text portlets or layout to break up the text a bit. > As an example the Community page currently wants to list everything linearly, > mailing lists, IRC, local lists, local user groups, conferences, etc. This is > too much and I've created a few subpages: "Mailing Lists", "IRC Channels", > "Sprints", "Conferences" and there should probably be a few others. I have also > added a folder "In your country", and there should be one page for each country, > each one can give informations on the local lists and user groups. I've not yet > moved the content +1, but let's keep the most important ones in the same place. > As a second example, the Project page text is too long. The text itself is ok, > but I believe it should be moved to subpages such as "History" or "Why zope" or > something. The entry page should only contain a very short introduction, with > links to the subprojects, and one only sentence that says "Zope has a long > history. Over a decade! Learn more (link-> History Page)". There are > interesting keywords (decade, mature, flexible, etc.) that must appear on the > entry pages and we should build very short sentences made with these keywords. +1 - feel free to re-organise > I personally find the Zope3 page extremely frightening, it currently begins with: > "It is nearly impossible to come up with an all-encompassing definition of > what "Zope 3" really is.". Yeah, I don't like that either. > => My first thought: "Ok, they don't know themselves what they did, I don't go > further, this is not for me". > > Again, we should list all the relevant keywords that represent Zope3, and build > a few short and positive sentences with these words. That's all. Long text must > be moved to subpages for people interested in reading further. > > Now a question: which old sites will be kept? Should we have to copy the tarball > release into the Plone site? I think we'll try to keep the entire current zope.org as old.zope.org, but move things over selectively to the new site if it makes sense. We'll deal with releases that people need to keep later, either via aliases or a wholesale move. Martin
-
Am 26.04.2008 um 11:24 schrieb Christophe Combelles: > Hi: > > I think there is too much text in some pages. Main pages are entry > points I think they should not be overloaded with contents. > > As an example the Community page currently wants to list everything > linearly, mailing lists, IRC, local lists, local user groups, > conferences, etc. This is too much and I've created a few subpages: > "Mailing Lists", "IRC Channels", "Sprints", "Conferences" and there > should probably be a few others. I have also added a folder "In > your country", and there should be one page for each country, each > one can give informations on the local lists and user groups. I've > not yet moved the content > +1 I just tried to sum up things! Mit freundlichen Grüßen Jan Ulrich Hasecke -- DZUG e.V. - Deutschsprachige Zope User Group - www.zope.de - www.dzug.org Forster Straße 29 - 06112 Halle/Saale Telefon +49 345 122 9889 9 - Fax +49 345 122 9889 1
PGP.sig (application/pgp-signature) 1 kB