Create urls/views/templates for dev-only views

[singingwolfboy]

Our designers find it helpful to be able to stub out simple views that aren't ready
to be seen for production yet, and check them into version control so that other
people can see them and provide feedback. This commit introduces a few new files
and directories for this purpose, as well as a sample view that will only be seen
in dev mode, and never in production.

[singingwolfboy]

Would it be better to define the dev-only urlpatterns at the top of views/dev.py, have urls.py import it from view/dev.py, and kill off urls_dev.py? Or is it better to keep the views and the urlpatterns in separate files?

[talbs]

Thanks, @singingwolfboy.

To help provide some context for this effort/request, there are two scenarios that this type of infrastructure would be helpful with:

1. Design/UI documentation: to help communicate design and UI patterns currently used, we could use views that help define elements, style options, and provide front-end examples of them. The design team has talked about views like this aiding with making new features' UI 1) consistent with any other similar elements in the app and 2) re-usable in the future if there are new patterns being made.
2. Design prototyping: for larger features or ones that design has more of a heads-up on, it'd be helpful to have a static space to jump into prototyping with that wouldn't 1) disturb the existing production-ready views of app and 2) require help from the development team to set up views in each individual case. These spaces could then be kept if the designer thinks its worth it for future documentation/refinement or removed once the branch/work is moved into delivery and production-level code/views are written.

@frrrances, we've talked recently about this. Feel free to chime in with any thoughts.

[frrrances]

@talbs pretty much summed up my feelings. Not sure how this will affect the dev/production split, but it would be helpful to have a static space where we can leverage the base html, sass, and js files but still have an area to really muck about.

[cahrens]

pylint errors in this file.

http://jenkins.edx.org:8080/job/edx-feature-branch-tests/9960/violations/file/cms/djangoapps/contentstore/views/dev.py/?

[cahrens]

👍 once pep8/pylint cleanup.