djangocms-cascade
DjangoCMS-Cascade is the Swiss army knife for working with Django CMS plugins.
Dis iz a FORK!
fix for django-reversion (already merged)
minor reordering of fields in Column Plugin
hopefully will be merged in the main repo, so this package is temporary
install with pip install tocka-djangocms-cascade
Original readme below…
Add DOM elements to a Django-CMS placeholder
DjangoCMS-Cascade is a collection of plugins for DjangoCMS >= 3.0.8 to add various HTML elements to any CMS placeholder in a hierarchical tree.
It allows web editors to layout their pages, without having to edit Django templates. In most cases, one template with one single placeholder is enough. The editor then can subdivide that placeholder into rows and columns, and add additional elements such as buttons, rulers, and much more.
Currently about a dozen compontents from Bootstrap-3.x are avialble, but Cascade makes it very easy to add additional compontents, often with less than 20 lines of Python code and without any database migrations.
Since all plugins share the same database table, it is very easy to build inheritance trees. For instance, Cascade’s own LinkPlugin inherits from a LinkPluginBase, which also is the parent of the ImagePlugin and the ButtonPlugin. This helps to share the common functionality required for linking.
Its pluggable
DjangoCMS-Cascade is very modular, keeping its CMS modules in functional groups. These groups have to be activated independently in your settings.py. It also is possible to activate only certain Plugins out of a group. One such group is cmsplugin_cascade.bootstrap3, but it could be replaced by a future Bootstrap-4, the Foundation, YUI or whatever other CSS framework you prefer.
Configurable individually
Each Cascade Plugin can be styled individually. The site-administrator can specify which CSS styles and CSS classes can be added to each plugin. Then the page-editor can pick one of the allowed styles to adopt his elements accordingly.
Reuse your data
Each Cascade Plugin can be configured by the site-administrator to share some or all of its data fields. This for instance is handy, to keep references onto external URLs in a central place. Or is can be used to resize all images sharing a cetrain property in one go.
Segment the DOM
It is even possible to group plugins into seperate evaluation contexts. This for instance is used to render different Plugins, depending on whether a user is authenticated or anonymous.
Responsive Images
In modern web development, images must adopt to the column width in which they are rendered. Therefore the <img ...> tag, in addition to the well known src attribute, also accepts additional srcset’s, one for each media query. DjangoCMS-Cascade calculates the required widths for each image, depending on the current column layout considering all media breakpoints.
News for next major release 0.5.0
Tested with django-cms 3.0.13 and Django-1.6.
Added SegmentationPlugin. This allows to conditionally render parts of the DOM, depending on the status of various request object members, such as user.
Setting CASCADE_LEAF_PLUGINS has been replaced by CMSPLUGIN_CASCADE_ALIEN_PLUGINS. This simplifies the programming of third party plugins, since the author of a plugin now only must set the member alien_child_classes = True.
Help needed
If you like this project, please invest some time and test it with Django-1.7/1.8, django-cms-3.1 and if possible Python-3.4.
With migrations added to Django-1.7, testing and developing plugins for django-cms get really messy. I currently have no resources to do all this cross-development.
Travis-CI worked for djangocms-cascade, Django-1.7 and django-cms-3.0.12, but since the last upgrade this is not the case anymore. If someone can find out why, it would be really great.
Features
Use the scaffolding technique from the preferred CSS framework to subdivide a placeholder into a grid system.
Make full usage of responsive techniques, by allowing stacked to horizontal classes per element.
Use styled buttons to add links.
Add <img> and <picture> elements in a responsive way, so that more than one image URL point onto the resized sources, one for each viewport using the srcset tags or the <source> elements.
Use segmentation the render parts of the DOM conditionally.
It is very easy to integrate additional elements from the preferred CSS framework. For instance, implementing the Bootstrap Carousel, required 50 lines of Python code and two simple Django templates.
Since all the data is stored in JSON, no database migration is required if a field is added, modified or removed from the plugin.
Currently Bootstrap-3.x is supported, but other CSS frameworks can be easily added in a pluggable manner.
In addition to easily implement any kind of plugin, DjangoCMS-Cascade makes it possible to add reusable helpers. Such a helper enriches a plugin with an additional, configurable functionality:
By making some of the plugin fields sharable, one can reuse these values for other plugins of the same kind. This for instance is handy for the image and picture plugin, so that images always are resized to predefined values.
By allowing extra fields, one can add an optional id tag, CSS classes and inline styles. This is configurable on a plugin and site base.
Detailed documentation
Find detailed documentation on ReadTheDocs.
Build status
History
This project started as a simple wrapper for the DjangoCMS TextPlugin, so that text elements could be shifted horizontally using the Grid System 960. Later on, support for 960.gs was dropped in favor of Twitter Bootstrap. Now the aim of the project is to fully support all Bootstrap components and more, so that djangoCMS can be used to build a website with as many widgets as possible, without having to edit templates.
DjangoCMS starting with version 3.0, allows to nest plugins inside other plugins. This feature made it possible to implement this kind of plugin.
License
Released under the terms of MIT License.
Copyright © 2015, Jacob Rief jacob.rief@gmail.com
1 maintainer
Metadata
1 maintainer
Release files for tocka-djangocms-cascade 0.6.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 | Actions |
|---|---|---|---|---|
| tocka-djangocms-cascade-0.6.0.1.tar.gz | 924.1 kB | Without provenance | Details for tocka-djangocms-cascade-0.6.0.1.tar.gz |
Release files / tocka-djangocms-cascade-0.6.0.1.tar.gz
| Download URL | tocka-djangocms-cascade-0.6.0.1.tar.gz |
|---|---|
| Size | 924.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
928896426395a5eae4499005967ab2f39147348adb17fd6573821f57e7608834
|
|
BLAKE2b-256 checksum How to use checksums |
df5079c9833e7d92f9cfa836a3dabf4cf42ce014c5dde1afb25d7a50fac06242
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tocka-djangocms-cascade 0.6.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
