A basic Django application to install often used static files.
With the convenience of an installable Django application, easily add some of the most widely used static files.
There are no templates included. If you want a skeleton application built on HTML5 Boilerplate and Twitter Bootstrap then checkout django-frontend-skeleton. If you want a light-weight template built on HTML5 Boilerplate without any static files then check out django-frontend-template.
Inactive
Django Frontend Static is now inactive. Please use django-frontend.
While continuing to use Django Frontend Static, be sure to force upgrade to avoid namespacing problems.
Read this article for more information.
Starring
More Information
For more information, instructions on how to get started, a changelog and a roadmap read the documentation.
Metadata
Release files for django-frontend-static 1.2.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-frontend-static-1.2.0.tar.gz | 1.4 MB | Without provenance | Details |
Release files / django-frontend-static-1.2.0.tar.gz
| Download URL | django-frontend-static-1.2.0.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3db1cd685bac0c3171a2c07dcf7d3f5c980bc646ef13e41490048a5260c2aca7
|
|
BLAKE2b-256 checksum How to use checksums |
91132500653279d19def4678625fa8721d8418fb0f24b1f3426438ee6d12aa32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-frontend-static 1.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.