collective.subsitebehaviors
====================
Features:
---------
Appearance customization for Dexterity types:
- logo applicable to any INavigationRoot, scaled using 'logo' scale if found
- end-user-friendly TTW-customizable CSS styling applicable to any INavigationRoot
Credits:
--------
- viewlets originally copied from ftw.subsite
- inspiration from various subsite packages
How to use:
-----------
- apply behavior to your content types as you wish
To define further appearance customization besides the logo, add 'styling fields to your
Dexterity type:
- field ids must start with the prefix "css_"
- css selector is encoded into field id as tag[tagname]_id[id]_class[classname]
- the CSS style can then be normally entered as the field value in the add / edit form
Here, only the tag value is mandatory, id & class are optional.
- optional css attribute name is encoded likewise as _cssattr[AttrName] suffix
Here, because Dexterity field names cannot contain dash (ie. '-') characters, the
CamelCase notation is used (as in 'AttrName', above). So for example background-color
css attribute is specified 'BackgroundColor'.
If there is no css attribute name found in the field id, it is assumed the field value
contains a full regular 'attribute: value' css style statement, without the ending
semicolon.
An example:
All this may sound complex at first sight, but it's really not- to define a custom
background color for your content, just add a Dexterity field whose id is
'css_tagbody_cssattrBackgroundColor'.
Contributors
============
- Petri Savolainen, petri.savolainen@koodaamo.fi
Changelog
=========
0.4 (5.9. 2015)
---------------
- properly require plone.behavior
- minor docs improvements
- fix browser layer name so tests will pass
- finish i18n bootstrap, w/ Finnish translations
0.3 (unreleased)
----------------
- showing fallback logo had been broken (sic) - fixed now
0.2 (unreleased)
----------------
- Styling & logo did not always work; fixed
0.1 (unreleased)
----------------
- Initial release.
[petri]
Metadata
Release files for collective.subsitebehaviors 0.4
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 |
|---|---|---|---|---|
| collective.subsitebehaviors-0.4.zip | 55.7 kB | Without provenance | Details for collective.subsitebehaviors-0.4.zip |
Release files / collective.subsitebehaviors-0.4.zip
| Download URL | collective.subsitebehaviors-0.4.zip |
|---|---|
| Size | 55.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a548a4eb82febb85e1f361fdbe402f5e56e094ceb2229417cd6265b6457d056
|
|
BLAKE2b-256 checksum How to use checksums |
f598f1ffee2b69f932b669ca61fb4d4a378a249a900c8c99fe4a641149bd3d8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.subsitebehaviors 0.4
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.