public
Last active

  • Download Gist
gistfile1.rst
reStructuredText

Diazo Theming sprint (part of the Plone OOTBT project)

May/June 2011

According to: http://pypi.python.org/pypi/plone.app.theming/1.0b5#packaging-themes there are several ways to package and deploy themes, but there is really only one way that is "new & exciting" that we should try to promote as "best practice": zip files. That is because zip files are universally understandable by anyone that knows how to use a computer. So, end users can easily install theme, and theme developers can easily create them. Python developers will likely continue putting them in Python packages, though.

For our purposes (i.e. rapid development of a number of attractive themes to coincide with the inclusion of Diazo/plone.app.theming in 4.2), I suggest we try to promote the "best of both worlds" by including the zip file contents in a Python package, that way we can produce zips that "scale" to the needs of developers. The risk is we alienate folks that see Python packages and run. I propose we mitigate that risk by making the zip files easily downloadable on plone.org.

This means:

  • Create a Python package of the form plonetheme.free_theme
  • Create a Diazo theme inside of the form: plonetheme.free_theme/plonetheme/free_theme/theme/free_theme/{rules.xml,index.html,static/}
  • Release the package to PyPI/plone.org
  • Create a zip file from the diazo theme and upload it to plone.org/products "by hand" (instead of including it in the package)
  • Include a link to the zip file in your documentation.
  • People contributing themes should have their logo/name/contact information in the footer. e.g. Theme by Styleshout, Plone integration by ACLARK.NET, LLC.

Use plonetheme.unilluminated as an example: https://github.com/aclark4life/plonetheme.unilluminated.

Preferably we develop themes in the Github collective: https://github.com/organizations/collective but SVN collective or elsewhere is fine too as long as they end up on PyPI/plone.org.

List of themes:

  1. Unilluminated (http://www.freecsstemplates.org/preview/unilluminated/) [aclark]
  2. CoolBlue (http://www.styleshout.com/templates/preview/CoolBlue10/index.html) [aclark]
  3. GrungeEra (http://www.styleshout.com/templates/preview/GrungeEra11/index.html) [aclark]
  4. Freshpick (http://www.styleshout.com/templates/preview/FreshPick10/index.html) [aclark]
  5. Jungleland (http://www.styleshout.com/templates/preview/Jungleland10/index.html) [mamico]
  6. KeepItSimple (http://www.styleshout.com/templates/preview/KeepItSimple11/index.html) [aclark]
  7. Flowerbuds (http://www.freewpthemes.net/preview/flowerbuds/) [toutpt]
  8. Enterprise (http://www.opendesigns.org/design/enterprise/) [esteele]
  9. Greyzed (http://wordpress.org/extend/themes/greyzed) [esteele]
  10. Earthlingtwo (http://www.freecsstemplates.org/preview/earthlingtwo) [amleczko]
  11. Pollination (http://www.freecsstemplates.org/preview/pollination) [nekorin]
  12. Motion (http://motiondemo.wordpress.com/) [davi-lima]

Once these are finished we can move on to discussing a better way to aggregate these themes for easy display and zip file download, possibly via:

Help

We are full up on themes (although of course you may still produce themes if you want to), but need Diazo-savvy folks to help with cleaning up theme rules. If you would like to help, please checkout this buildout:

That and Github Collective access should allow you to easily make improvements to any targeted theme (I can add themes to the buildout as needed, just ask.)

Please sign in to comment on this gist.

Something went wrong with that request. Please try again.