https://github.com/clintecker/django-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.
https://github.com/clintecker/django-chunks

Last synced: 3 months ago
JSON representation

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.

• Host: GitHub
• URL: https://github.com/clintecker/django-chunks
• Owner: clintecker
• License: bsd-3-clause
• Created: 2009-11-15T19:07:09.000Z (about 15 years ago)
• Default Branch: master
• Last Pushed: 2023-11-22T09:26:05.000Z (about 1 year ago)
• Last Synced: 2024-07-15T15:42:10.777Z (5 months ago)
• Language: Python
• Homepage: http://github.com/clintecker/django-chunks
• Size: 156 KB
• Stars: 303
• Watchers: 7
• Forks: 101
• Open Issues: 11
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
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.

This is really nothing more than a model and a template tag.

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.

### Why would anyone want this? ###

Well it essentially allows someone to define "chunks" (I had wanted to call it blocks, but that would be very confusing for obvious reasons) of content in your template that can be directly edited from the awesome Django admin interface.  Throwing a rich text editor control on top of it make it even easier.

### Usage: ###

    {% load chunks %}

    

      

        Test

      

      

        
 Blah blah blah

        


            ...

        

        


            {% chunk "home_page_left" %}

        

        


            {% chunk "home_page_right" %}

        

      

    


if you need the `Chunk` object in the template (maybe you've added some generic relations to it) you should use the `{% get chunk %}` templatetag:

    {% load chunks %}

    {% get_chunk "home_page_left" as chunk_obj %}

    

    
{{ chuck_obj.content }}


This is really helpful in those cases where you want to use `django.contrib.flatpages` but you need multiple content areas.  I hope this is helpful to people and I'll be making minor edits as I see them necessary.