Drop-in replacement for the StreamField in Wagtail.
This work was funded thanks to a Kickstarter campaign!
It relies on react-streamfield, a React package created for the occasion.
This work is currently in beta phase and will in the end be merged in Wagtail. You should be careful and manually check that it works for your own StreamField and report any bug you find.
Requirements
Wagtail 2.6 or above.
Getting started
It’s really easy to setup, like most NoriPyt packages:
pip install wagtail-react-streamfield
Add 'wagtail_react_streamfield', to your INSTALLED_APPS before 'wagtail.admin', 'wagtail.images', 'wagtail.docs' & 'wagtail.snippets'
That’s it!
Usage
wagtail-react-streamfield has the same class API as the regular StreamField. What changes:
Meta attributes (or passed to __init__)
- closed
Set to True to close all blocks of this type when loading the page. Defaults to False.
Screenshots
1 maintainer
Metadata
1 maintainer
Release files for wagtail-react-streamfield-django-3 1.3.5
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 | |
|---|---|---|---|---|
| wagtail-react-streamfield-django-3-1.3.5.tar.gz | 142.9 kB | Without provenance | Details |
Release files / wagtail-react-streamfield-django-3-1.3.5.tar.gz
| Download URL | wagtail-react-streamfield-django-3-1.3.5.tar.gz |
|---|---|
| Size | 142.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
980f16081d6f272eee2a99107355aab703a33eb019c098b5d7daf057ebe2d1ac
|
|
BLAKE2b-256 checksum How to use checksums |
9c2ce026c77d4b53c22cee13f03c811701ca09220892f97430a169b72703bb78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.7.4
|
Security for wagtail-react-streamfield-django-3 1.3.5
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.
