Personal tools
Skip to content. | Skip to navigation
plonetheme module
A theme intended for use with mobile theming control panel (zettwerk.mobiletheming). The theme uses plone.app.themingplugins to override templates just for this theme. These templates will not work if you duplicate the theme TTW (themingplugins do not work for that) Usage You probably want to use the theme like this: install zettewerk.mobiletheming install medialog.mobilethemeTwo go to the mobile theming control panel and choose which url that should have the mobile theme. It is of course possible to enable the theme in diazo theme control panel and use it as a regular theme When you want to edit the theme, you should do this on the file system. If you duplicate it TTW, the overridden templates will not be used.
Barceloneta is the name of the Plone 5 default theme. It's named after the Barcelona beach and neighbourhood. Barceloneta is a Diazo theme made from scratch using modern frontend technologies. It's responsive and spans throught all the Plone UI including the CMS backend part. It's based on Bootstrap 3, but it's not dependent of it in any way. Although it reuses some of the structure and good practices of the original Bootstrap, it has its own personality and is fully adapted to Plone. Structure Barceloneta uses LESS as a pre-processor to generate the resultant stylesheet. The LESS resources live in the plonetheme.barceloneta egg in the plonetheme/barceloneta/theme/less directory: plonetheme/barceloneta/theme/less ├── accessibility.plone.less ├── alerts.plone.less ├── barceloneta-compiled.css ├── barceloneta-compiled.css.map ├── barceloneta.css ├── barceloneta.plone.export.less ├── barceloneta.plone.less ├── barceloneta.plone.local.less ├── behaviors.plone.less ├── breadcrumbs.plone.less ├── buttons.plone.less ├── code.plone.less ├── contents.plone.less ├── controlpanels.plone.less ├── deco.plone.less ├── discussion.plone.less ├── dropzone.plone.less ├── event.plone.less ├── fonts.plone.less ├── footer.plone.less ├── forms.plone.less ├── formtabbing.plone.less ├── grid.plone.less ├── header.plone.less ├── image.plone.less ├── loginform.plone.less ├── main.plone.less ├── mixin.borderradius.plone.less ├── mixin.buttons.plone.less ├── mixin.clearfix.plone.less ├── mixin.forms.plone.less ├── mixin.grid.plone.less ├── mixin.gridframework.plone.less ├── mixin.images.plone.less ├── mixin.prefixes.plone.less ├── mixin.tabfocus.plone.less ├── modal.plone.less ├── normalize.plone.less ├── pagination.plone.less ├── pickadate.plone.less ├── plone-toolbarlogo.svg ├── portlets.plone.less ├── print.plone.less ├── roboto ├── scaffolding.plone.less ├── search.plone.less ├── sitemap.plone.less ├── sitenav.plone.less ├── sortable.plone.less ├── states.plone.less ├── tables.plone.less ├── tablesorter.plone.less ├── tags.plone.less ├── thumbs.plone.less ├── toc.plone.less ├── tooltip.plone.less ├── tree.plone.less ├── type.plone.less ├── variables.plone.less └── views.plone.less They are divided by base styling, layout, function, components and views, so they could be easily reusable and extended from other themes. The main LESS resource that imports all the others is barceloneta.plone.less. It has a set of LESS variables that can be overriden either through the web using the Theming control panel or by reusing it in your own theme. They include colors, sizes, fonts and other useful parameters. Barceloneta makes use of the new Diazo bundle to expose its resources to Plone using the Resource Registries. As it is a pure Diazo theme, it keeps a low profile being Plone agnostic and only containing the theme itself. Changes from previous versions of Plone Regarding markup and comparing to the previous versions of Plone, Barceloneta introduced lots of changes in the default Plone markup to modernize it and make it more accessible. There are few parts of rendering Plone that were not updated. However, any class or id that was stripped away from Plone was done with the purpose of making upgrades and adaptations of existing Diazo themes easy. Whenever possible additional classes and ids were introduced being always domain namespaced plone-*.
plonetheme.bootstrap integrates Twitter Bootstrap CSS/JS framework into Plone. You can checkout the framework at http://twitter.github.com/bootstrap It overrides some templates and uses javascript to transform some markup in order for it to work correctly. It's not perfect, but it's close. This product is based in Twitter Bootstrap version 2.3.x. This product adds both the basic CSS file and also the Responsive one to have a mobile-enabled site from the start. The generated markup is based on 'fluid CSS' and it contains a 12 column grid. The basic HTML markup is a mix of plonetheme.sunburst and Twitter Bootstrap and it uses the same approach of constructing the columns as Sunburst Theme: a simple view that returns the classes needed to have the correct column widths. If you want to change those widths, just override the view following the common Plone overriding patterns. This product is intended to be used in two scenarios: As a theme from Plone As a base theme to build Plone themes for your site following 'old practices' Some designers prefer to work following the old best-practices instead of using the Diazo-way-of-theming, this product is for them. You can create a theme package (check templer skeleton generator), and base your theme on this one.
An installable theme for Plone 4
This theme implements the look of Plone 3 and earlier in a separate package, and is supplied for backwards compatibility reasons, and for people who prefer the old theme over the new standard one in Plone 4.
This is Plone 4’s default theme “Sunburst” reimplemented with Diazo.
Features Customize styles in control panel. Responsive design for tablets and smartphones Special path bar with children Layout customizations Theme is SCSS based and styles most things with variables which can easily be customized in a control panel. Just visit the customization view: http://localhost:8080/Plone/customstyles_form Additional SCSS You can easily register custom SCSS files in your addon package using ZCML, if you need to customize more than available through the web: <configure xmlns:theme="http://namespaces.zope.org/plonetheme.onegov"> <include package="plonetheme.onegov" /> <theme:add_scss path="resources/custom.scss" /> </configure> The SCSS files can also be restricted to a specific context interface or a specific request layer. Be aware that the context interface applies to the context the styles are rendered on, which is either the Plone site root or an INavigationRoot object. <configure xmlns:theme="http://namespaces.zope.org/plonetheme.onegov"> <include package="plonetheme.onegov" /> <theme:add_scss path="resources/custom.scss" for="my.package.interfaces.ISubsite" layer="my.package.interfaces.IMyPackageLayer" /> </configure> Special path bar For another fast way to navigate between content, this theme includes a special path bar, which shows the breadcrumb's children. This behavior can be disabled in the plone.app.registry, using the setting plonetheme.onegov.flyout_breadcrumbs. https://raw.github.com/OneGov/plonetheme.onegov/master/docs/screenshot_flyout_breadcrumbs.png Links Github project repository: https://github.com/OneGov/plonetheme.onegov Issue tracker: https://github.com/OneGov/plonetheme.onegov/issues Continuous integration: https://jenkins.4teamwork.ch/search?q=plonetheme.onegov
Goals Keep the theme color-neutral (black, white, grays), so it meshes with any company logo and doesn't feel like it requires color adjustment for doing the 10-minute-show-it-to-the-boss exercise. The theme does not use any tables for layout, and is based on the Deco grid approach which is currently in use on plone.org. It works perfectly in all browsers, including IE6. The grid works in both fixed-width and flexible-width modes, there's a commented-out section in the top of the CSS file you can enable if you want fixed-width layout. No substantial markup changes outside of the table removal - class and ID names are kept. The theme uses some CSS3 features, but degrades gracefully. The theme does not use any DTML. When viewed on a device with less than 640px width, the portlets neatly tuck under the main content area. This means that the site works well with CSS-enabled devices like tablets and phones that may have limited resolution.
Plumi video sharing system For more info see http://plumi.org For installation instructions see docs/INSTALL.txt For migration instructions see docs/MIGRATE.txt For the Plumi Manual visit http://en.flossmanuals.net/Plumi/Introduction Code repository: https://github.com/plumi/plumi.app Questions and comments to discuss@lists.plumi.org Report bugs at http://plumi.org/newticket