Personal tools
You are here: Home Products Plone Roadmap #229: Change root-of-Zope page for Unified Install
Document Actions

#229: Change root-of-Zope page for Unified Install

Contents
  1. Definitions
  2. Motivation
  3. Assumptions
  4. Proposal
  5. Implementation
  6. Deliverables
  7. Risks
  8. Progress log
  9. Participants
by Joel Burton last modified August 6, 2008 - 18:22
Change the default page at the root of Zope for the Unified installer to give helpful information for the novice user.
Proposed by
Ian Anderson
Seconded by
Joel Burton
Proposal type
Architecture
Assigned to release
State
being-discussed

Definitions

 

Motivation

The default Zope root page is not helpful for novice users of Plone and can often be confusing. There is no information about why a user might be seeing this page, and why there is no mention of Plone.

Assumptions

This is only for the Plone installer

Proposal

The page displayed at the root of Zope should be changed to include the following.

  1. A message such as "did you mean http://___/Plone ?". It is important to make this a link to the root of the Plone site.
  2. A link to the ZMI
  3. A link to the help file on Plone.org explaining what to do if you are locked out of your site
  4. A link to the documentation on Plone.org on Virtual hosting, and a brief message about how a misconfiguration of VHM can cause you to see this page

For political reasons, it is important to preserve the Zope name, and logo on the page. We propose that this can be accomplished by including the Zope logo, and Plone logo at the bottom of the page. THese logos should be of equivalent size.

Implementation

The installer should replace the default Zope page at install time.

Deliverables

  1. A .zexp of the proposed new example page will be created and discussed. This can be added to any site for testing purposed.
  2. Python code to update the Zope index_html method will be written.
    • unit tests will need to be written
  3. Translation/localization of this is not required for success of this project; however, the translation teams may choose to translate this new content.
  4. No new documented is expected.

Risks

 

Progress log

Thanks to wiggy's pointer to the bones code, this is working with the Unified Installer (via content creation -- not .zexp).

I assume that we'll have some attention paid to the contents of the start page. Here's the first draft:

First Draft of Plone replacement for ZMI root page

Participants

 

+1

Posted by Wichert Akkerman at August 2, 2008 - 14:11
We already implemented this for the Jarn Plone hosting environment a couple of months ago. We can release that code if anyone is willing update this to work in our installers (SteveM, I'm looking at you)

+0.5

Posted by Hanno Schlichting at August 3, 2008 - 07:53
I think the idea is good in general.

I'm wondering if the /Plone link is really the id of the currently installed default Plone site, if that is the case this should be changed to something like /site. Plone is a registered trademark and you don't want your web site to fall under the terms of use policy for our trademark.

I don't think a zexp is a good idea to distribute anything, since it makes it very hard to maintain it. Creating two images and replacing one text is easily doable in Python code.

Regarding translation, I think this content doesn't need to be translated. It is aimed at users who will also look at the ZMI, which is the English-only admin interface or need to configure Apache rewrite rules or other means of sysadmin work, in which case they will need to know English in almost all cases.

Re: +0.5

Posted by Wichert Akkerman at August 3, 2008 - 21:51
.zexp is horrible and should never be used. I gave SteveM the code we use for the Jarn hosting setup which achieves this by directly running a simple script using zopectl.

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by