django-stack-it

Content management system: Pages is a list of (ordered) block and relevant content. Though to allow inline i18n content management, with high performance usage.


Keywords
django_stack_it
License
MIT
Install
pip install django-stack-it==0.1.18

Documentation

django-stack-it

Codacy Badge https://api.codacy.com/project/badge/Coverage/a842b7f950cd465d91d6b06c7d56ce16 https://travis-ci.org/VingtCinq/django_stack_it.svg?branch=master

Content management system under development

Quickstart

Install django-stack-it:

pip install django-stack-it

Django Stack It relies on several dependencies, you need to add to your INSTALLED_APPS

INSTALLED_APPS = (
    ...
    'polymorphic_tree',
    'polymorphic',
    'mptt',
    'imagekit',
    'stack_it'
    ...
)

Add django-stack-it's URL patterns:

To avoid migration messup, we strongly recomend you to deport Stack It migrations to your project. This will avoid any unexpected conflict between environements, due to language addition/deletion. In your settings:

Basic Usage

As soon as you a model is linked to a URL, it should inherit from the Page model.

Article is now considered to be a Page. It comes with several usefull fields like title, slug dans template_path.

Register your model to the admin the way you want, and you can see all your website organization within one unified admin doing:

Article or any other model won't show up in the admin anymore. Each model and model instances will be managed from the "Page" admin, where all your pages are organized in a Drag n Drop interface to build up your site structure.

If you want your model's to be registered as usual, add show_in_index = True in your admin class to allow

Features

  • TODO

Running Tests

Does the code actually work?

source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install tox
(myenv) $ tox

Credits

Tools used in rendering this package: