Wagtail Content Import is a module for importing page content into Wagtail from third-party sources. Page content is imported into a StreamField, using a set of customisable mappings. Currently, it supports:
As sources:
- Google Docs
- OneDrive/SharePoint
As files:
- Google Docs documents with:
- Rich text
- Tables
- Images
- Headings
- Docx files with:
- Text with bold and italics
- Headings
Requirements:
- Python >= 3.10
- Django >= 4.2
- Wagtail >= 7.0
For the full documentation, see: https://torchbox.github.io/wagtail-content-import/
Note for Google Import
If using Google Docs import, for users to authenticate with Google they must either allow third party cookies or add accounts.google.com to their allowed domains (Settings/Privacy and Security/Cookies and other site data in Chrome or Preferences/Privacy & Security in Firefox).
4 maintainers
Metadata
4 maintainers
Release files for wagtail-content-import 0.13.3
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 |
|---|---|---|---|---|
| wagtail_content_import-0.13.3.tar.gz | 20.2 kB | With provenance | Details for wagtail_content_import-0.13.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wagtail_content_import-0.13.3-py3-none-any.whl | Python 3 | none | any | Details for wagtail_content_import-0.13.3-py3-none-any.whl |
Total release size: 53.9 kB
Release files / wagtail_content_import-0.13.3.tar.gz
| Download URL | wagtail_content_import-0.13.3.tar.gz |
|---|---|
| Size | 20.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af063456d5f364fc1bed72e645647417c748bc4f54b07e15c64927c8cd8fe520
|
|
BLAKE2b-256 checksum How to use checksums |
25620e91f08638eb71bb855174c92986c5a3610d4d42d07df9ba145c33939a6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logRelease files / wagtail_content_import-0.13.3-py3-none-any.whl
| Download URL | wagtail_content_import-0.13.3-py3-none-any.whl |
|---|---|
| Size | 33.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63ebf231790af0cdc62ab75f607aa8b0536764a80f92c92e02a740fe544ed911
|
|
BLAKE2b-256 checksum How to use checksums |
88c84fb985b34c5e58b82e103051522799cb82b50c73b5712c04079da283d6a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logSecurity for wagtail-content-import 0.13.3
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for wagtail_content_import-0.13.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logA 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.
