EasyNewsletter

EasyNewsletter is a simple but powerful newsletter/mailing product for Plone.

http://plone.org/products/easynewsletter

collective.plonetruegallery

A gallery/slideshow product for plone that can aggregate from picasa and flickr or use plone images.

http://plone.org/products/plone-true-gallery

Singing & Dancing - Gerenciador de informativo para o Plone

The all-singing all-dancing newsletter product for Plone.

http://plone.org/products/dancing
Project Description Singing & Dancing
* Translated into 18 languages
* Downloaded more than 20,000 times
* Increasing year-over-year development activity
* Large, active development team
* Established codebase

Manual: http://www.webtide.co.za/how-to/singing-dancing-user-manual

Adventures In Theming – The Complete Saga (tutorial)

I’m working on a large-scale inventory management system built as a series of Plone content types. It’s primary focus is on scientific research labs in a university setting. This means we’ll have a lot of individual labs with specific needs using the system in different ways. I took on the task of building a generic, centralized theme that each lab theme can extend. I wanted to define a specific look for the system, but also allow instances to be tailored for end users.

http://lionfacelemonface.wordpress.com/tutorials/adventures-in-theming-the-complete-saga/

How to write templates for Plone 4

Como escrever templates para o Plone 4 - Plone 4 has some improvements in templates. This is an overview of the most important ones, and what you need to know when updating your existing templates.

• Macros, slots, viewlets and other monsters. 
• Viewlet managers.
• Templates for an object's view.
• General templates other than objects' views.
• Related items.
• Disabling columns.
• Removal of redundant IDs and classes for the content area.
• Portal status message.

http://plone.org/documentation/kb/how-to-write-templates-for-plone-4

Do Plone ao Wordpress

Matando mosquito com bala de canhão / Simplificando a vida com o Wordpress

"Com tudo isso, fiz a migração do meu site do Plone para o Wordpress. Com ele consegui dinamizar o processo de gerenciamento e publicação de conteúdo, e pude estender o Wordpress de forma bem mais simples e rápida do que vinha fazendo com o Plone".
http://imasters.com.br/artigo/16559/cms/do-plone-ao-wordpress

Designing for Content Management Systems

Designing and indeed front-end development for a website that will have content edited by non-technical users poses some problems over and above those you will encounter when developing a site where you have full control over the output mark-up. However, most clients these days want to be able to manage their own content, so most designers will find that some, if not all, of their designs end up as templates in some kind of CMS.
By considering the CMS as you design, you can maintain far more control over the final output. If your designs will be implemented and integrated into the CMS by a developer, then taking control at the design phase will help you to keep control over the design as opposed to leaving decisions to the developer or the content editors.

• Know your enemy
• Keep it consistent
• Do not assume content length or height of blocks
• Avoid using image replacement for text
• Consider the CMS when designing navigation
• Design and create CSS rules for all possible HTML elements
• Assume HTML elements can be stacked in any order
• Use CSS to enforce the style guide and semantics
• Test with real content
• Help your content editors to maintain the design
• Further resources

http://coding.smashingmagazine.com/2010/11/22/designing-for-content-management-systems/

Plone Theme Reference (para Plone 4 e Plone 3)

http://plone.org/documentation/manual/theme-reference