caktus / django-comps

A utility that provides an entry point for integrating front end designers into a django project

django-comps

An app that facilitates rapid prototyping.

Provides an entry point for deeper integration of front end designers with little to no experienceinto a project.

Features

Protypes can be built in the COMPS_DIR and render within he context of a Django project, without the need for defined views.

• Take advantage of the templating engine
• No need to pre-configure urls and views during prototyping
• Onboard new designers to the wonders of Django

Installation

django-comps requires Django >= 1.4 and Python >= 2.6.

pip install django-comps

Documentation

Documentation on using django-comps is available on Read The Docs.

License

django-comps is released under the BSD License. See the LICENSE file for more details.

Contributing

If you think you've found a bug or are interested in contributing to this project check out django-comps on Github.

django-comps's Issues

Add TOX

Management Command to output static HTML files & resources

It might be nice to have a management command to output an archive of static resources to be able to hand off to an interested party, so that they would not necessarily need to stand up a django site to see the comps.

comps_listing should not extend base.html

By default, the comps_listing template should be an unstyled, unextended listing template.

This allows true beginners to start working with the app with no template dependencies that might not yet exist in a new project.

TTW Zip Export

On the listing page for the comps dir, it would be nice to hookin/repurposes the management command's static dump and output a zip file

Support subfolders in comps directory

• Refactor comp_listing to utilize an optional directory slug.
• Recator comp to redirect to comp-listing with the directory slug, if a template is not found

Limit comp_listing to find only .html and directories

The little .DS_Store file that macs add into folders shows up on the comp listing. Is there a way to exclude those? Are there other files that appear on other systems that you'd want to exclude in that list?

Restrict the output of the filesystem reading to .html files and directories.

Utilize RTD and extend documentation

Zip Export behaves oddly with compressor

Need to inspect when the renderer gathers resources from /static/.

At present, it appears that for projects using compressor, the renderer gathers resources before compressor caches files.

The current workaround is to zip export 2x.

Remove comp_listing.html from example app

Artifact of an earlier version.