Magplan
Project management system for publishers, magazines and content creators, written on the top of Django Framework.
Features
- complete posts management: from article idea to publishing;
- articles stages, assignees, roles;
- posts metadata, editors, authors, attachments (images, PDF's, files);
- extendable Markdown engine with ability to use external one;
- posts ideas with voting system;
- discussions, email notifications;
- team actions logs;
- publish content to S3 and WordPress with async tasks.
Development
This project uses uv for dependency management. Make sure you have uv installed:
curl -LsSf https://astral.sh/uv/install.sh | sh
Run development
This will install development dependencies:
make devel
Publish a New Version
To create a new version, follow these steps:
-
Make sure all your changes are committed.
-
Run one of the following commands to bump the version in pyproject.toml:
For a major version bump (e.g., 1.0.0 -> 2.0.0)
make bump-version TYPE=major
For a minor version bump (e.g., 1.0.0 -> 1.1.0)
make bump-version TYPE=minor
For a patch version bump (e.g., 1.0.0 -> 1.0.1)
make bump-version TYPE=patch
*Commit the changes to the repository.
- Create a git tag with the new version:
make create-tag
- Push the changes and new tag to trigger the CI/CD pipeline:
git push origin
git push origin --tags
The CI/CD pipeline will automatically build and deploy the new version when it detects the new tag.
Version Number Format
- MAJOR: Incremented for incompatible API changes
- MINOR: Incremented for backward-compatible functionality additions
- PATCH: Incremented for backward-compatible bug fixes
Current Version
The current version can be checked by running:
grep 'version = ' pyproject.toml
LICENSE
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Metadata
Release files for magplan 3.6.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 |
|---|---|---|---|---|
| magplan-3.6.1.tar.gz | 80.5 kB | Without provenance | Details for magplan-3.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| magplan-3.6.1-py3-none-any.whl | Python 3 | none | any | Details for magplan-3.6.1-py3-none-any.whl |
Total release size: 199.7 kB
Release files / magplan-3.6.1.tar.gz
| Download URL | magplan-3.6.1.tar.gz |
|---|---|
| Size | 80.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e10de14c2bbe1302d050f40493881723e330821c42a3ef4669e7dd92a5fffd9
|
|
BLAKE2b-256 checksum How to use checksums |
1e5c6d648049b22727016d94ff00ea9bca3cb95a7f98681e55cfb37256d00169
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / magplan-3.6.1-py3-none-any.whl
| Download URL | magplan-3.6.1-py3-none-any.whl |
|---|---|
| Size | 119.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab88ed3b02f2ab5058911bd0391b53398381d909831ad01581c2c64c6971bbd8
|
|
BLAKE2b-256 checksum How to use checksums |
2ed45de48a302577e28dc72fb2b048822eade68f2cfa025c11668f9e4b77e347
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for magplan 3.6.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.