# wagtailcommonblocks [](https://pypi.python.org/pypi/wagtailcommonblocks)
> Common StreamField blocks for Wagtail.
*Check out [Awesome Wagtail](https://github.com/springload/awesome-wagtail) for more awesome packages and resources from the Wagtail community.*
## Quickstart
Assuming you have a [Wagtail](https://wagtail.io/) project up and running:
```sh
pip install wagtailcommonblocks
```
Add commonblocks to your `settings.py` in the INSTALLED_APPS section, before the core wagtail packages:
```python
...
'commonblocks',
'wagtail.contrib.wagtailsitemaps',
...
```
# Available blocks
* CommonPageChooserBlock
* SimpleRichTextBlock
* CommonImageBlock
* CommonQuoteBlock
* CommonHeadingBlock
* CommonVideoBlock
* CommonInternalLink
* CommonExternalLink
* CommonLinksBlock
You can override the headings of the `CommonHeadingBlock` block:
```python
...
COMMONBLOCKS_HEADING = (
('h1', 'h1'),
('h2', 'h2'),
)
```
## Development
### Releases
- Make a new branch for the release of the new version.
- Update the [CHANGELOG](https://github.com/springload/wagtailcommonblocks/CHANGELOG.md).
- Update the version number in `setup.py`, following semver.
- Make a PR and squash merge it.
- Back on master with the PR merged, use `make publish` (confirm, and enter your password).
- Finally, go to GitHub and create a release and a tag for the new version.
- Done!
> Common StreamField blocks for Wagtail.
*Check out [Awesome Wagtail](https://github.com/springload/awesome-wagtail) for more awesome packages and resources from the Wagtail community.*
## Quickstart
Assuming you have a [Wagtail](https://wagtail.io/) project up and running:
```sh
pip install wagtailcommonblocks
```
Add commonblocks to your `settings.py` in the INSTALLED_APPS section, before the core wagtail packages:
```python
...
'commonblocks',
'wagtail.contrib.wagtailsitemaps',
...
```
# Available blocks
* CommonPageChooserBlock
* SimpleRichTextBlock
* CommonImageBlock
* CommonQuoteBlock
* CommonHeadingBlock
* CommonVideoBlock
* CommonInternalLink
* CommonExternalLink
* CommonLinksBlock
You can override the headings of the `CommonHeadingBlock` block:
```python
...
COMMONBLOCKS_HEADING = (
('h1', 'h1'),
('h2', 'h2'),
)
```
## Development
### Releases
- Make a new branch for the release of the new version.
- Update the [CHANGELOG](https://github.com/springload/wagtailcommonblocks/CHANGELOG.md).
- Update the version number in `setup.py`, following semver.
- Make a PR and squash merge it.
- Back on master with the PR merged, use `make publish` (confirm, and enter your password).
- Finally, go to GitHub and create a release and a tag for the new version.
- Done!
Metadata
Release files for wagtailcommonblocks 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 | |
|---|---|---|---|---|
| wagtailcommonblocks-0.1.tar.gz | 11.6 kB | Without provenance | Details |
Release files / wagtailcommonblocks-0.1.tar.gz
| Download URL | wagtailcommonblocks-0.1.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c279351db1bbcaf7c9a6ce3aaa9ce8dcd0184472ad32f325e247acfb8d82ff74
|
|
BLAKE2b-256 checksum How to use checksums |
71ca4d7fb541291de2ed90a0ac49c2a26f9007873cdff691b4149002828907d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wagtailcommonblocks 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.