This release is a pre-release and may not be stable for production use.
collective.collectionepilog
Provides a behavior for collections to add epilog RichText field under the collection results.
The content of the epilog will be added to the collection views via collection-epilog viewlet below the content.
Installation
Install collective.collectionepilog with
pip:
pip install collective.collectionepilog
or uv:
uv add collective.collectionepilog
Contribute
Prerequisites ✅
- An operating system that runs all the requirements mentioned.
- uv
- Git
Development 🔧
-
Clone this repository, then change your working directory.
git clone git@github.com:collective/collective.collectionepilog cd collective.collectionepilog
Add features using plonecli or bobtemplates.plone
This package provides markers as strings (<!-- extra stuff goes here -->) that are compatible with plonecli and bobtemplates.plone.
These markers act as hooks to add all kinds of subtemplates, including behaviors, control panels, upgrade steps, or other subtemplates from plonecli.
To run plonecli with configuration to target this package, run the following command.
plonecli add <template_name>
For example, you can add a content type to your package with the following command.
plonecli add content_type
You can add a behavior with the following command.
plonecli add behavior
You can check the list of available subtemplates in the [`bobtemplates.plone` `README.md` file](https://github.com/plone/bobtemplates.plone/?tab=readme-ov-file#provided-subtemplates).
See also the documentation of [Mockup and Patternslib](https://6.docs.plone.org/classic-ui/mockup.html) for how to build the UI toolkit for Classic UI.
License
The project is licensed under GPLv2.
Credits and acknowledgements 🙏
A special thanks to all contributors and supporters!
Metadata
Release files for collective-collectionepilog 0.1.0a6
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_collectionepilog-0.1.0a6.tar.gz | 141.6 kB | Without provenance | Details for collective_collectionepilog-0.1.0a6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective_collectionepilog-0.1.0a6-py3-none-any.whl | Python 3 | none | any | Details for collective_collectionepilog-0.1.0a6-py3-none-any.whl |
Total release size: 170.1 kB
Release files / collective_collectionepilog-0.1.0a6.tar.gz
| Download URL | collective_collectionepilog-0.1.0a6.tar.gz |
|---|---|
| Size | 141.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38f7b80affdcda78292b5829e2fdc518ed7a8e1e58881fd2d0eb3d7941a6049b
|
|
BLAKE2b-256 checksum How to use checksums |
df3fed68fe0ef3852fbb6184c8144dcc8731d84aca72449eb454a4436a1d8c35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / collective_collectionepilog-0.1.0a6-py3-none-any.whl
| Download URL | collective_collectionepilog-0.1.0a6-py3-none-any.whl |
|---|---|
| Size | 28.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e97273c6e7341641decd6c407ad944e08e14af06b3c2093526b2c28ce3e62d6
|
|
BLAKE2b-256 checksum How to use checksums |
70547e3e7559cbe7866781b4a727ef49bc06490ddb8d9ab5655d9283429ef0b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for collective-collectionepilog 0.1.0a6
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.