27.01.2015 Views

Best Practices of Plone Development

Best Practices of Plone Development

Best Practices of Plone Development

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1.2 Products 1 BEST PRACTICES FOR PLONE DEVELOPMENT<br />

1.2.6 Framework: skins/<br />

• Contains the skin folders<br />

– Not the skins directly<br />

• Skin folder convention is lower-cased, no-space version <strong>of</strong> product name<br />

1.2.7 Framework: Extensions<br />

• Install.py script install product<br />

– Detailed later<br />

• External methods for this product<br />

– Works same as site-wide external methods (in instance Extensions)<br />

– Except “Module name” includes Product<br />

∗ eg, YourProduct.ExternalMethodFile<br />

1.2.8 Framework: doc/<br />

• Documentation directory<br />

• Not used by <strong>Plone</strong><br />

1.2.9 Framework: VERSION.txt<br />

• Should contain just version number (“1.0.1”)<br />

• Shown in <strong>Plone</strong> control panel<br />

• Easy way to tell what version is installed<br />

12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!