About django-better-chunks

Think of it as flatpages for small bits of reusable content you might want to insert into your templates and manage from the admin interface.

By adding chunks to your installed apps list in your Django project and performing a ./manage.py syncdb, you'll be able to add as many "keyed" bits of content chunks to your site.

The idea here is that you can create a chunk of content, name it with a unique key (for example: home_page_left_bottom) and then you can call this content from a normal template.

Example Usage

{% load chunks %}
        <h1> Blah blah blah</h1>
        <div id="sidebar">
        <div id="left">
            {% chunk "home_page_left" %}
        <div id="right">
            {% chunk "home_page_right" %}

This is really helpful in those cases where you want to use django.contrib.flatpages but you need multiple content areas.

django-better-chunks is a fork off Clint Ecker's project django-chunks. It adds i18n multi-language support and lets you tie chunks to sites if you're using django.contrib.sites.


Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.