Django Addendum
Change snippets of copy on your site, on the fly, for any application, and without a full-fledged CMS.
Solving queries like:
Hey, we need to change the greeting on login from “Hi!” to “Sup?”
And:
The footer copy needs to be updated.
And:
The marketing team would really like to be able to change that message on a monthly basis. I don’t care that that’s a third-party appliwhoozitz!
This is all simple stuff and it’s probably coded right into your templates. Changing it is easy enough, but requires a developer and then a release. Boo!
Usage
Just add addendum_tags to your templates:
{% load addendum_tags %}
{% snippet 'home:greeting' %}Hi!{% endsnippet %} {{ user.first_name }}
<footer>
{% snippet 'home:footer' %}© 2011 by Acme Corp.{% endsnippet %}
</footer>
Now you can edit content for these placeholders from the admin interface. If you don’t add anything or you delete text, the site text will always revert to what is in the template.
Use it for small bits of user modifiable text from any template on your site, and for swapping out -lorem ipsum- text when prototyping.
Find some more information in the docs
Installation
Install the package from PyPI:
pip install django-addendum
Add it to your INSTALLED_APPS tuple:
INSTALLED_APPS += ('addendum')
Contributing
Contributions are welcome but should follow some basic guidelines to make life easier:
Pull requests should be made from distinct branches that include only the requested changes branched from the canonical master branch.
Include tests for bug fixes and new features. Ensure that your Travis build is passing before submitting the pull request.
Include documentation for any new features.
For multi-commit updates please squash commits so the packager maintainer only has at most a few commits to review.
Please limit changes to your specific pull request (excluding extraneous changes and please do not bump the version for your own changes).
License
BSD licensed.
Testing
To run the tests, clone the repository and install tox.:
pip install tox
Then use the command:
tox
To run the tests against specified (or all) environments.
Otherwise, install the test requirements in requirements.txt and then run the py.test comand. tox is recommended.
1 maintainer
Metadata
1 maintainer
Release files for django-addendum 0.6.0
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 | |
|---|---|---|---|---|
| django-addendum-0.6.0.tar.gz | 7.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_addendum-0.6.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 18.9 kB
Release files / django-addendum-0.6.0.tar.gz
| Download URL | django-addendum-0.6.0.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40dc89de2ee78e6895b78e11c76e1a8d5d68b9d8412bd2d68efe40b9e92a93be
|
|
BLAKE2b-256 checksum How to use checksums |
99f044fa3fdbb9275aab8fa4933bab571063e47e14607dd95496cf495481d46d
|
| 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/46.0.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.6.10
|
Release files / django_addendum-0.6.0-py2.py3-none-any.whl
| Download URL | django_addendum-0.6.0-py2.py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
29953b53213fab7ac480cd24d6c21a3219bae87d6b795407354a6b3df6ebc854
|
|
BLAKE2b-256 checksum How to use checksums |
d0a765e054cec598c585f5642e9da5ecbcd10ae28e8049e6efe8a3291ff94c00
|
| 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/46.0.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.6.10
|
Security for django-addendum 0.6.0
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.
