This release is a pre-release and may not be stable for production use.
provides many css and color schemes to customize the site layout.
Together, the two allow quick and easy customization of the Plone skin.
If you want this functionality, you should install medealog.subskins.
It will pull this product as a dependency.
If you want to write a product similar to subskins read ahead.
PloneSubSkins allows to switch to specific CSS files handling such or such aspects of your Plone skin.
By default, this hacked version of PloneSubSkins manage the following categories:
- Base
- Top
- Navigation
- Text
- Global navigation
- Portlets
- Bottom
- Extra (multiple choices)
Another category is dedicated to manage your different base_properties files, named MySkin_colorschemes.
To use PloneSubSkin you just need to respect the following naming convention:
1 - if your skin product is named MySkin, the navigation-related CSS must be stored in a sub-folder named MySkin_navigation,
text related CCS must be in MySkin_text, etc.
It will produce the following directory structure:
/Products
/MySkin
/skins
/MySkin
main_template.pt
some.gif
other.pt
/MySkin_colorschemes
bluetheme_base_properties.prop
yellowtheme_base_properties.prop
/MySkin_navigation
navYellow.css
navYellow2.css
/MySkin_text
small.css
normal.css
all_arial.css
/MySkin_globalnav
globalnav.css
globalnavOld.css
/MySkin_calendar
cal1.css
cal2.css
etc.
2 - In your css files, add the following line:
<dtml-with get_base_properties mapping>
before the existing line:
<dtml-with base_properties> (do not remove this)
and add the line
/* </dtml-with> */
at the end of the file
3 - Depend on this product in your metadata.xml
4 - Put a file named subskins_choices.xml in your profile directory
You can modify those categories or add your own ones by editing /Products/PloneSubSkins/AppConfig.py
Changelog
=========
4.1
___
Switched to using select boxes (instead of multiselect) for the "extra" selections so its easier to see what is selected.
4.0
---
* Plone 4.0 compatible
* Added multiselect extra category
* Use titles to list css in the form
3.2
---
* Live preview of selected css without page reload.
3.1
----------------
* Initial release
Release files for Products.PloneSubSkins 4.2dev-r146816
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Products.PloneSubSkins-4.2dev-r146816.tar.gz | 35.0 kB | Without provenance | Details for Products.PloneSubSkins-4.2dev-r146816.tar.gz |
Release files / Products.PloneSubSkins-4.2dev-r146816.tar.gz
| Download URL | Products.PloneSubSkins-4.2dev-r146816.tar.gz |
|---|---|
| Size | 35.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
632b8dec5f4a5fc4a87acda1ba5c1d6ba8798ab92fe09b946c0c8ad828a6a450
|
|
BLAKE2b-256 checksum How to use checksums |
346073aaba9677ca581e1a582066cd47b9d90dd244a676e2547cc75b935d205b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.PloneSubSkins 4.2dev-r146816
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.
