http://dev.plone.org/plone/ticket/10280
related ticket: * http://dev.plone.org/plone/ticket/8795 Motivation: Currently the title tag comes from a viewlet: plone.htmlhead.title, registered for the viewletmanager plone.htmlhead in plone.app.layout.viewlets. If you want to write a .pt with a custom <title> tag you're out of luck: the discrimination for the viewlet registration is on the context and the request, the template used is not involved in the adapter lookup. Plone is correctly being advertised as having strong SEO features, but #1 of the list at http://www.sixfeetup.com/blog/2010/8/20/10-reasons-why-plone-can-improve-your-seo can be improved resolving this issue: all views with portal as context currently don't provide a meaningful title (and that is also an accessibility issue). Proposal: the <title> tag should be in a macro on his own. This would allow a template to override it. It should come from a view, not a viewlet. Reason: viewlets are good when you don't know in advance how many snippets you need in some place; views are good when you know you will need one snippet AIU. Title tag belongs to the second category. Risks: people relying on the old behaviour to customize the title will have to change their code, or the resulting html page will have two <title> tags. Silvio _______________________________________________ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team