Django CMS Slick Slider Plugin
A Django CMS Slider Plugin with Slick Slider.
Features
Add a Slick Slider to any page via Django CMS Plugin
Change/set Slick options via JSONField
Set some styling options such as color
CMS
Admin Form
Output
Documentation
The full documentation is at https://djangocms-slick-slider.readthedocs.io.
Quickstart
Install djangocms_slick_slider:
pip install djangocms-slick-slider
Add it to your INSTALLED_APPS:
INSTALLED_APPS = (
...
'djangocms_slick_slider.apps.DjangocmsSlickSliderConfig',
...
)
Example project
You can quickly get an example project up to test / develop the plugin.
If you have virtualenvwrapper installed:
git clone https://github.com/oesah/djangocms_slick_slider.git cd example mkvirtualenv my_project_env pip install -r requirements.txt python manage.py runserver
Visit your homepage (usually http://localhost:8000).
User: admin
Password: adminadmin
You should see some instances of the Slick Slider plugin. You can play around to see, how it works.
Settings
SLICK_SLIDER_VERSION
Version of Slick Slider that should be used. Keep in mind, that this version needs to be in static/vendor/ folder with the appropriate folder name.
If you want to upgrade, download and copy the new version into the before mentioned folder and change the version in the settings.
Default: 1.8.0
SLICK_SLICKER_DEFAULT_OPTIONS
You can adjust the default options by setting SLICK_SLICKER_DEFAULT_OPTIONS to a dictionary.
Default:
SLICK_SLICKER_DEFAULT_OPTIONS = {
'dots': True,
'slidesToShow': 2,
'mobileFirst': False,
'slidesToScroll': 1,
'autoplay': True,
'autoplaySpeed': 1500
}
You can set any option that slick-slider offers. You can find them here: https://kenwheeler.github.io/slick/
SLICK_SLIDER_ACE_THEME
You can change the ACE theme of the edit field in the admin.
Default: json
SLICK_SLIDER_ACE_MODE
You can change the ACE mode of the edit field in the admin.
Default: github
Running Tests
Does the code actually work?
source <YOURVIRTUALENV>/bin/activate (myenv) $ pip install tox (myenv) $ tox
If you have issues with different python versions, please take a look at these docs: https://www.holger-peters.de/using-pyenv-and-tox.html
Release to PyPi
For versioning, you need to have standard-version installed:
yarn install
Once you are ready and everything has been commited to git, you can run:
yarn run release
This will:
Bump the version in the according files
Commit everything to git and create a git tag
Create a package for PyPi and upload it
Push everything to Git including tags
Credits
Tools used in rendering this package:
ToDos
translations
Metadata
Release files for djangocms-slick-slider 1.0.7
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 |
|---|---|---|---|---|
| djangocms-slick-slider-1.0.7.tar.gz | 49.0 kB | Without provenance | Details for djangocms-slick-slider-1.0.7.tar.gz |
Release files / djangocms-slick-slider-1.0.7.tar.gz
| Download URL | djangocms-slick-slider-1.0.7.tar.gz |
|---|---|
| Size | 49.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84c5d679ca412dcd12c8941d3964734bd5174d67ebde72bd56961b47810c51dc
|
|
BLAKE2b-256 checksum How to use checksums |
7273f465484b97141b6b86ac8258ab8c74c963e97faeebdb0b6caf1391a87e84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Security for djangocms-slick-slider 1.0.7
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.