-
DIY Plone Style
-
by
David Convent
—
last modified
Feb 16, 2011 02:13 AM
—
filed under:
plone skin,
templating,
skin layer,
skinfolder,
skins,
design,
examples,
skin,
plone skins,
Presentation,
tutorial,
development tips,
Development,
style,
skin skinning plone portal_skins,
Interfaces,
stylesheet,
skinselector,
template,
products,
Visual Themes,
development,
source code,
HowTo,
Documentation,
howto,
Skin Switching,
skins layers,
NewProduct,
CSS,
templates,
ploneCustom.css customizing css by role,
documentation,
Skins,
Themes,
Design,
Customization,
filesystem,
example
A tutorial/skeleton product for creating your own theme (visual style) for Plone.
Located in
Download & Extend
-
Collective
-
by
Jon Stahl
—
published
Apr 23, 2006
—
last modified
Feb 13, 2009 01:29 AM
—
filed under:
Collective,
Development,
Products,
product development,
source code
The Collective is a community code repository for Plone Products and other add-ons, and is a useful place to find the very latest code for hundreds of add-ons to Plone. Developers of new Plone Products are encouraged to share their code via the Collective so that others can easily find it, use it, and contribute fixes and improvements.
Located in
Documentation
/
Glossary
-
Software home
-
by
John Samuel Anderson
—
published
Jan 09, 2009
—
last modified
Jan 09, 2009 10:43 PM
—
filed under:
filesystem,
python,
source code,
zope
The directory inside the Zope installation (on the filesystem) that contains all the Python code that makes up the core of the Zope application server. The various Zope packages are distributed here. Also referred to as the $SOFTWARE_HOME environment variable. It varies from one system to the next, depending where you or your packaging system installed Zope. You can find the value of this in the ZMI > Control Panel.
Located in
Documentation
/
Glossary
-
Zope instance
-
by
John Samuel Anderson
—
published
Jan 09, 2009
—
last modified
Sep 11, 2009 03:58 PM
—
filed under:
source code,
zope
An operating system process that handles HTTP interaction with a Zope database (ZODB). In other words, the Zope web server process. Alternatively, the Python code and other configuration files necessary for running this process.<br />
One Zope installation can support multiple instances. Use the buildout recipe plone.recipe.zope2instance to create new Zope instances in a buildout environment.<br />
Several Zope instances may serve data from a single Data.fs using a ZEO server on the back-end.
Located in
Documentation
/
Glossary
-
Python path
-
by
John Samuel Anderson
—
published
Jan 09, 2009
—
last modified
Jan 09, 2009 10:47 PM
—
filed under:
python,
source code
The order and location of folders in which the Python interpreter will look for modules.
It's available in python via sys.path.
When Zope is running, this typically includes the global Python modules making up the standard library, the interpreter's site-packages directory, where third party "global" modules and eggs are installed, the Zope software home, and the lib/python directory inside the instance home.
It is possible for python scripts to include additional paths in the Python path during runtime. This ability is used by zc.buildout.
Located in
Documentation
/
Glossary
