Django application to display on the frontend the list of notifications and run some basic actions such as “view all notifications”, “delete notifications”, it also provides helpers to display notifications.
This works with twitter bootstrap (http://twitter.github.com/bootstrap/) but can easily be adapted with other front-end frameworks.
Documentation
Extensive documentation is available on ‘Read the Docs’: http://django-frontend-notification.readthedocs.org
Contributing
If you’ve found a bug, implemented a feature or customized the template and think it is useful then please consider contributing. Patches, pull requests and suggestions are welcome!
Source code: http://github.com/areski/django-frontend-notification
Bug tracker: https://github.com/areski/django-frontend-notification/issues
License
Copyright (c) 2011-2014 Star2Billing S.L. <info@star2billing.com>
django-frontend-notification is licensed under MIT, see MIT-LICENSE.txt.
Credit
django-frontend-notification is a Star2Billing-Sponsored Community Project, for more information visit http://www.star2billing.com or email us at info@star2billing.com
Metadata
Release files for django-frontend-notification 1.0.4
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-frontend-notification-1.0.4.tar.gz | 42.8 kB | Without provenance | Details |
Release files / django-frontend-notification-1.0.4.tar.gz
| Download URL | django-frontend-notification-1.0.4.tar.gz |
|---|---|
| Size | 42.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ef7f6e9e25e90c261f15bc1f2ba186b3e85db60d6b3da46c2eb18981eb8941c
|
|
BLAKE2b-256 checksum How to use checksums |
30e6040fbc74a7afe0cde8c534c4f5db277e435b034f167f0d3688c8f1075538
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-frontend-notification 1.0.4
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.