Skip to main content
For when you don't need no stinkin' CMS

Makes things ever-so-slightly easier when you just want to serve a bunch of pages
that are just rendered templates (with no special views or context)

Routing autogeneration
----------------------

define STATICPAGES_TEMPLATES in your settings.py as a series of
(section_name, base_url, base_template_path) three-tuples:

STATICPAGES_TEMPLATES = [
('homesite', '', 'homesite'),
('subsite', 'url/of/subsite', 'staticpages/subsite'),
]

make a directory-and-page hierarchy there, and the files will be automatically served with properly-named urls

URL patterns are named by the site section name, and have a parameter for
the path: reverse('sectionname', args=('path/to/file'))

For example:

$PROJECT_ROOT/templates/homesite/
- index.html
- pricing.html
- about/
- index.html
- team.html
- news.html

reverse('homesite', args=('about/team') -> '/about/team'


TODO
====

Menu activation
---------------


http://110j.wordpress.com/2009/01/25/django-template-tag-for-active-class/



Sitemaps
--------

http://minimoesfuerzo.org/2011/02/12/sitemaps-django-static-pages/

Metadata

Release files for django-staticpages 0.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-staticpages 0.2.3
File Size Uploaded Provenance Actions
django-staticpages-0.2.3.tar.gz 3.3 kB Without provenance Details for django-staticpages-0.2.3.tar.gz

Release files / django-staticpages-0.2.3.tar.gz

Download URL django-staticpages-0.2.3.tar.gz
Size 3.3 kB
Tags Source
SHA-256 checksum
How to use checksums
097e629ed7c245948ad54a984858d05aef731403ecadd49dcf1dc88512ac201e
BLAKE2b-256 checksum
How to use checksums
fbbfa764f4d6f870c2d02ef83eb772758ea6752ad4903cf6ec248d4cd8323705
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for django-staticpages 0.2.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.

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.

Release history Release notifications | RSS feed

This release

0.2.3 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page