# Mezzanine File Collections
Mezzanine File Collection is a simple file container page type for the Django / Mezzanine CMS.
The Mezzanine’s core gallery module only deals with images. I got frustrated with it, I quickly developed an alternative to handle any filetype.
Most of this app’s code is directly inspired from the Mezzanine’s core.
## Installation
Installation is quite simple.
$ pip install mezzanine-file-collections
Add “mezzanine_file_collections” to your list of installed apps. Then migrate your database. That’s it.
## Usage
Once installed, just create a new “File collection”, and upload your files the usual way.
The default templates uses Bootstrap’s media objects for a basic rendering, but it’s very easy to overwrite it. Just look into the template.
1 maintainer
Metadata
1 maintainer
Release files for mezzanine-file-collections 1.0.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 | |
|---|---|---|---|---|
| mezzanine-file-collections-1.0.1.tar.gz | 6.8 kB | Without provenance | Details |
Release files / mezzanine-file-collections-1.0.1.tar.gz
| Download URL | mezzanine-file-collections-1.0.1.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1344312af98e66c4a80bebe525f860229bc9a70830659dbd258e12eddcecf94
|
|
BLAKE2b-256 checksum How to use checksums |
a6c4ee317d54a3f0343586c216579b12aeeb75d4a443f19b38cc14fc78dabd91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mezzanine-file-collections 1.0.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.
