For years we have supported the same import ordering rules in our CONTRIBUTING.md files as part of the Pinax coding style. One feature of this was separate sections for both django and django.contrib. Time has come for that to change.
Since 2011, we’ve been packaging templates for Pinax apps inside pinax-theme-bootstrap. Over the
years we’ve moved more and more app templates that used to be bundled with the app into the theme.
Unfortunately, we are too coupled to specific Bootstrap versions.
Inspired by Linux distributions like Ubuntu, James Tauberproposed a different approach to releasing Pinax apps and starter projects. As a result of James’s proposal we announced Pinax 16.04 last month and explained as well the benefits of the approach as the rough plan we were going to follow.
We have been big fans of ReadTheDocs and have hosted
our documentation there since its earliest days. Sphinx was at one time the only
real option for writing docs and having ReadTheDocs build and host them.
For a while now, we’ve been maintaining a theme we use in all our projects based
on Bootstrap, Font Awesome, and jQuery. Up until today, we have just vendored
the static assets and included them by leveraging Django staticfiles finders.
The Pinax team has built a lot of reusable Django apps over the years. We have
begun settling on certain patterns to make our apps more consistent. In this
post we’d like to share with you the different aspects of what we are doing and