Skip to main content
...::contents

I. Introduction
===============

A collective phantasy dynamic theme.
Based on three colors.

II. Installation
================

Read docs/INSTALL.txt to install this package in your zope instance
using buildout or easy_install (read it carefully ! there's an overrides
section)

In your Plone site > ZMI > portal_quickinstaller

Choose "Three Colors Theme" product, and click on Install
This will install the plone product and all dependencies
(collective.phantasy and SmartColorWidget)

III. Usage
==========

1. Change skin for the portal :
-------------------------------

- Go to your plone site > dynamic-root-skin

- click on edit

- change the 3 colors,

- change the dimensions and other fields values

- set filenames for some fields

- load your custom css or images inside the skin
using "Import Files" form (post a zip with all your files)
or using PloneFlashUpload (a powerful Plone product)

- take care of filenames inside the skin
(they must be the same as names inside the skin edit form, perhaps you will need to change
the values because Plone has changed them for valid ids).

2. change a skin for a folder :
-------------------------------

- Go to your plone site > folder-skins-repository

- Add a new phantasy skin inside the skins repository

- In this new skin you will get the same values as set in dynamic-root-skin

- Change it (do the same thing as you've done in $1)

- Go to any folder on your site for which you want another skin

- Click on "edit" tab

- A "phantasy-skin" field is available
so you can browse the portal to choose another skin for your folder.

- Note that the folder get the two css (from the root skin and from the folder skin)


3. Create a new skin with Samples provided in this product
----------------------------------------------------------

- Add a new dynamic skin (see $1 & $2)

- Click on import images and files

- Inside the folder alternate_skin, choose the archive alternate_skin.zip click on Import

- Read howtouseit.txt (to set values according to new images)

- There is another example inside ornicart_skin Folder






collective.threecolorstheme Installation
========================================

To install collective.threecolorstheme into the global Python environment (or a workingenv),
using a traditional Zope 2 instance, you can do this:

* When you're reading this you have probably already run
``easy_install collective.threecolorstheme``. Find out how to install setuptools
(and EasyInstall) here:
http://peak.telecommunity.com/DevCenter/EasyInstall

* If you are using Zope 2.9 (not 2.10), get `pythonproducts`_ and install it
via::

python setup.py install --home /path/to/instance

into your Zope instance.

* Create a file called ``collective.threecolorstheme-configure.zcml`` in the
``/path/to/instance/etc/package-includes`` directory. The file
should only contain this::

<include package="collective.threecolorstheme" />

* Create a file called ``collective.threecolorstheme-overrides.zcml`` in the
``/path/to/instance/etc/package-includes`` directory. The file
should only contain this::

<include package="collective.threecolorstheme" file="overrides.zcml" />

.. _pythonproducts: http://plone.org/products/pythonproducts


Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:

* Add ``collective.threecolorstheme`` to the list of eggs to install, e.g.:

[buildout]
...
eggs =
...
collective.threecolorstheme

* Tell the plone.recipe.zope2instance recipe to install a ZCML slug:

[instance]
recipe = plone.recipe.zope2instance
...
zcml =
collective.threecolorstheme
collective.threecolorstheme-overrides

* Re-run buildout, e.g. with:

$ ./bin/buildout

You can skip the ZCML slug if you are going to explicitly include the package
from another package's configure.zcml file.


Changelog
=========

SVN -UNRELEASED
---------------

*

0.1
---

* Initial release

Metadata

Release files for collective.threecolorstheme 0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for collective.threecolorstheme 0.1
File Size Uploaded Provenance Actions
collective.threecolorstheme-0.1.zip 310.2 kB Without provenance Details for collective.threecolorstheme-0.1.zip

Built distribution (wheel)

Table of built distributions (wheels) for collective.threecolorstheme 0.1
File Interpreter ABI Platform Actions
collective.threecolorstheme-0.1-py2.4.egg Legacy Egg format - - Details for collective.threecolorstheme-0.1-py2.4.egg

Total release size: 622.4 kB

Release files / collective.threecolorstheme-0.1.zip

Download URL collective.threecolorstheme-0.1.zip
Size 310.2 kB
Tags Source
SHA-256 checksum
How to use checksums
af1d6329ff1eca9f5e48fa898331a71129e13d6dbd732cfd9270a747f22a911d
BLAKE2b-256 checksum
How to use checksums
d565227896be16b401413046c0b92c779e5e0a1e8d77bf0bc0439ee4786372cc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / collective.threecolorstheme-0.1-py2.4.egg

Download URL collective.threecolorstheme-0.1-py2.4.egg
Size 312.2 kB
Tags Egg
SHA-256 checksum
How to use checksums
77153a94a8afe66a109508f1c1c66a2185686115865826d48d6d5bf913e80629
BLAKE2b-256 checksum
How to use checksums
6bec89e4c3b60d8728082ad9582a04630a318805f64b5ca47b36777dd3b0ee4d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for collective.threecolorstheme 0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page