Plone Themes Free Extra Quality Download
Perla Hockins
We should show them off (along with other current themes) on plone.org in the download section, with nice screen shots. On GitHub, the theme add-ons other than Vikas' in the collective are mostly missing screen shots.
Since they'll be Diazo themes, I would think they'd be downloadable as zip files and uploadable to your site, entirely through the web. So... no need to involve buildout and in fact once a nice new MAINTAINED gallery exists in plone.org (or wherever, online), we could add a feature to plone.app.theming to include at least a link to the gallery or, even better, add a feature to integrate the gallery and theme installation from the gallery.
the Plone.org/download page now has a section on themes. Yes it's a (slow) start, but it's a start. There is a folder in there (currently excluded from nav) for themes, for when we are ready to do something more significant and less manual perhaps. Then we can have the theming control panel include a link to (for example) Plone.org/download/themes or somesuch.
Thanks Espen. Yeah, you are right. @b4oshany's work improving the theme editor will help make it easier to develop themes, rather than putting emphasis on showcasing themes. Even so, as we get more open source themes (or even paid themes), it will be nice to preview them on your site.
I don't think it's a great idea to ship themes that are buggy... at the very least we need to fix the obvious bugs. We would get burned when a newcomer tried them out and immediately found bugs; they would come away thinking that the quality of the shipped themes was a reflection of the quality of the underlying software. The reason we include PloneFormGen in our buildout.cfg (commented out) is that it really is a top flight quality add-on.
However, I wholeheartedly agree with your overall suggestion of shipping at least one more lovely theme with Plone, or making it super easy for someone to view a plone.org theme gallery from their @@theming-controlpanel and download/install one of those themes.
For convenience, Plone themes often comprise a number of separate style sheets, but for speed and efficiency, in production mode, Plone has a mechanism (portal_css) for packaging these up into just one or two files.
As a matter of course, the last style sheet to load on every Plone page is ploneCustom.css. You'll see this if you inspect the HTML head tag of your page using Firebug. If you dig further, you'll probably find that this style sheet is completely empty. By the rules of precedence in the CSS Cascade, any styles in this sheet will override styles specified in the preceding sheets. So you have a "blank sheet" here for your own customizations.
When you click on ploneCustom.css you'll find that you can't edit it. The next stage is to put the ploneCustom.css in a place where it can be edited. You'll see a Customize option just above the grey text area, click the Customize button and you'll find that the style sheet has been automatically copied to portal_skins/custom.
If you've installed Plone 4 with the Sunburst theme, the ploneCustom.css comes with a number of commented out pre-packaged styles that you might like to experiment with. You can override the layout styles to a fixed width and alter the colors of the links.
plone.css is automagically generated dynamically based on the full portal_css registry configuration. It is used in e.g. TinyMCE to load all CSS styles into the TinyMCE in a single pass. It is not used on the normal Plone pages.
Since jbot is already included in the bobtemplates.plone theme skeleton viaplone.app.themingplugins, you can start using it immediately by adding all thetemplates you want to override in thesrc/plonetheme/tango/theme/template-overrides directory.
For instance, to override path_bar.pt (the breadcrumbs) from plone.app.layout, knowingthat this template is found in a sub folder named viewlets, you need to namethe overriding template plone.app.layout.viewlets.path_bar.pt.
The path to the original template is plone/app/event/browser/event_view.pt,so the full dotted name for our replacement template should be:plone.app.event.browser.event_view.pt.Create a new file with this dotted name into the template-overrides folder.
To render our dynamic content for the slider we need a custom view in Plone.There are various ways to create Views.For now, we will use a very simple template-only-view via jbot andthemingplugins.The bobtemplates.plone skeleton includes everything you need.
df19127ead