This release is a pre-release and may not be stable for production use.
Case Study for Plone
Showcase Plone usage with case studies
The backend package for Case Study for Plone — a Plone 6 add-on that provides content types to be used in Plone sites. See also the frontend package @plone-collective/volto-casestudy.
Features
collective.casestudy provides two new content types to be used in Plone sites, Case Study and Provider.
Case Study
A case study of a Plone deployment, which has attributes to track the Plone version used, the industry, and the type of usage of Plone.
Provider
A company providing Plone services and solutions.
See it in action
collective.casestudy is being used in the following sites:
Documentation
This package supports Plone sites using Volto, and you should install the frontend package @plone-collective/volto-casestudy in your project.
Installation
Add collective.casestudy to the Plone installation using uv:
uv add collective.casestudy
or add it as a dependency on your project package's pyproject.toml
dependencies = [
...
"collective.casestudy",
],
Start Plone and activate the plugin in the addons control-panel.
Source Code and Contributions
We welcome contributions to collective.casestudy.
You can create an issue in the issue tracker, or contact a maintainer.
Development
You need a working Python environment version 3.10 or later.
Then install the dependencies and a development instance using:
make install
By default, we use the latest Plone version in the 6.x series.
License
The project is licensed under GPLv2.
Credits and acknowledgements 🙏
Generated using Cookieplone (2.0.0b3) and cookieplone-templates (f4f4d41) on 2026-08-04 12:41:09.957188. A special thanks to all contributors and supporters!
1 maintainer
Metadata
1 maintainer
Release files for collective.casestudy 2.0.0a4
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 | |
|---|---|---|---|---|
| collective_casestudy-2.0.0a4.tar.gz | 1.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| collective_casestudy-2.0.0a4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / collective_casestudy-2.0.0a4.tar.gz
| Download URL | collective_casestudy-2.0.0a4.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c875104bf9fbe097a8010c0a36e2c40013bd33013e5741c31baea3a70c7a54cf
|
|
BLAKE2b-256 checksum How to use checksums |
974ff14bf60a137700561a2c88a10d8438ab1cff301570a63fa57b4358462eae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / collective_casestudy-2.0.0a4-py3-none-any.whl
| Download URL | collective_casestudy-2.0.0a4-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2a2b7968189c165e24eb609d28ad047b6f3ad95fa69529d075d52299cd6000a
|
|
BLAKE2b-256 checksum How to use checksums |
8fad28936e05162dc42d262ba744ff8b83027e809f1294836eaf497452eef0cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for collective.casestudy 2.0.0a4
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.
