Skip to main content

Serve different templates and static files for eg. mobi and web. Layers can be stacked to enable resource re-use.

Project description



django-layers makes it possible to serve a set of templates and static resources as defined in This means you can serve different HTML, Javascript and CSS to eg. basic mobile devices, smart phones and desktop browsers. These template sets (aka layers) also stack, so if you create foo.html for basic devices it is automatically available for desktop browsers as well. You can override foo.html for desktop browsers.


  1. Install or add django-layers to your Python path.

  2. Add layers after django.contrib.static to your INSTALLED_APPS setting.

  3. Ensure the app that you will be creating layers for appears first in INSTALLED_APPS else template override won’t work.


Note: there is a working example in the example subdirectory.

We have sites, and Each of the sites have their own, thus different Django processes.

Directory structure

    - basic
        - foo.html (1)
        - bar.html (2)
    - smart
        - bar.html (3)
    - web
        - bar.html (4)

    - basic
        - foo.css (5)
        - bar.css (6)
    - smart
        - bar.css (7)
    - web
        - bar.css (8)


We define an “inheritance” hierarchy.

  • Desktop settings has LAYERS = {'layers': ['basic', 'web']}.

  • Basic settings has LAYERS = {'layers': ['basic']}.

  • Smart settings has LAYERS = {'layers': ['basic', 'smart']}.

All settings require loaders and finders to be set. The order is important.




Template results

Static results

Overriding templates from other apps

The normal template resolution rules apply. Creating eg. templates/web/registration/login.html will override the login page for web only.


Collectstatic remains unaffected. The collector delegates to finders, so all layer aware resources end up with partial paths under the STATIC_ROOT directory.


A user could follow a link that leads him to a layer that serves a broken page. For example a web site is served on with an accompanying basic site Visiting with a basic device like a Samsung E250 will result in the user being redirected to That page probably does not exist for basic devices because it can’t render it well enough. In such a case a decorator exclude_from_layers is provided that renders a friendly page instead of a 404 or 500 error:

class WebOnlyView(TemplateView):
    template_name = "layers/web_only_view.html"

    def get(self, *args, **kwargs):
        return super(WebOnlyView, self).get(*args, **kwargs)


  • Hedley Roos



  1. Inevitable package rename.


  1. Initial release.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-layers-hr-1.9.tar.gz (15.4 kB view hashes)

Uploaded Source

Built Distribution

django_layers_hr-1.9-py2.7.egg (37.0 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page