Theme and Layout¶
ploneintranet.theme is deprecated, use
What used to be
ploneintranet.theme has been factored out to a separate package
quaive.resources.ploneintranet to facilitate easy per-project theming tweaks without
having to fork the main code base.
For backward compatibility reasons, the theme browser layer is retained to not break existing installs. You should not use ploneintranet.theme.
resources as defined in the Ploneintranet Prototype.
It also provides a
++theme++ploneintranet.theme static resource traverser to gain access to
theme supporting images. We’ve kept the old name for backward-compatibility reasons.
The intent is, that you can replace the theme for easy CSS and Diazo based restyling.
No ploneintranet.* packages should depend on
quaive.resources.ploneintranet - it will not
be present in customized client installs.
No browser logic should be placed in
The only browser view in
quaive.resources.ploneintranet is a
Note that much of our frontend design is expressed in view markup that is not set by the theme, but rather across the whole ploneintranet code base.
Add browser logic to the package
whose content it renders, or to
ploneintranet.layout if it’s generic view logic.
ploneintranet.layout contains browser views needed to support
(c.q. your client-specific variant replacing that package).
It is separate from the
quaive.resources.ploneintranet Diazo theme to separate “theme as CSS”
concerns from “theme as layout” concerns.
All “system-wide” browser logic shared across ploneintranet.* packages should go into
It contains a number of generic view components, like the homepage Dashboard.
It defines and supports App-specific Browser Layers to enable per-app view overrides for default Plone content types.
It also contains a static resource directory which is traversable as
which you can use to place and access global resources like images.
++theme++ploneintranet.layout in your browser view templates.
No package should use
++theme++ploneintranet.theme since that would introduce a unwanted