Introduction
SnakeSkin allows skin products for Plone 3 to be created easily in a similar way to the ZopeSkel plone3_theme template. The primary difference is that plone3_theme assumes either a blank theme or a customisation of the default, whereas snakeskin allows the user to select the theme he wants to customise.
This is very useful for commercial environments where a generic skin requires small modifications on a client-by-client basis.
An example using an internal teamrubber skin is:
Nimbus:teamrubber.snakeskin matthewwilkes$ paster create -t plone3_snakeskin Selected and implied templates: ZopeSkel#basic_namespace A project with a namespace package teamrubber.snakeskin#plone3_snakeskin A Theme for Plone 3.1 based on another theme egg. Enter project name: clienttheme.example Variables: egg: clienttheme.example package: clientthemeexample project: clienttheme.example Enter namespace_package (Namespace package (like clienttheme)) ['clienttheme']: clienttheme Enter package (The package contained namespace package (like example)) ['example']: example Enter version (Version) ['1.0']: 1.0 Enter theme_name (The name of this theme) ['Client Skin']: Client Skin Enter base_theme (The package containing the theme to base on (the name of the egg)) ['plonetheme.example']: plonetheme.example Enter basename (The name of the Zope skin layer the above theme provides) ['My Theme']: My Theme Enter description (One-line description of the package) ['A theme based on an existing arbitrary plone 3 theme.']: This is my client customisation of the defaults for plone3_theme. Enter long_description (Multi-line description (in reST)) ['']: I'm not feeling talkative. Enter author (Author name) ['']: Matthew Wilkes Enter author_email (Author email) ['']: matt.wilkes@teamrubber.com Enter keywords (Space-separated keywords/tags) ['']: Enter url (URL of homepage) ['']: Enter license_name (License name) ['GPL']: Enter zip_safe (True/False: if the package can be distributed as a .zip file) [False]:
Changelog
1.1
- Fix skins.xml template precedence.
[MatthewWilkes]
- Simplify options
[MatthewWilkes]
1.0
- Initial concept, includes some ideas from OOTB plone themes, but not all
[MatthewWilkes]
Metadata
Release files for teamrubber.snakeskin 1.1
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 | |
|---|---|---|---|---|
| teamrubber.snakeskin-1.1.tar.gz | 8.6 kB | Without provenance | Details |
Release files / teamrubber.snakeskin-1.1.tar.gz
| Download URL | teamrubber.snakeskin-1.1.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abe7ad1e89bc518454f6f2593cbf7bc0ef3ac9914cc2ebb426b15beac38c676b
|
|
BLAKE2b-256 checksum How to use checksums |
81522286dd11bcf11f40e472b5f4f6267099abad441ee1075dbdb99cb63b19f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for teamrubber.snakeskin 1.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.