Project code for django markdown tutorial

[robalford]

Where to put new files:

• New files should go into a top-level subfolder, named after the article slug. For example: my-awesome-article

How to merge your changes:

1. Make sure the CI code style tests all pass (+ run the automatic code formatter if necessary).
2. Find an RP Team member on Slack and ask them to review & approve your PR.
3. Once the PR has one positive ("approved") review, GitHub lets you merge the PR.
4. 🎉

[bzaczynski]

@robalford Thanks for the pull request.

I downloaded your fork and made sure that everything works as expected. There's one or two minor tweaks remaining before we can merge. Can you change the directory structure, please?

Thanks!

[bzaczynski]

Can you move the README file one level up, please? Alternatively, I'm wondering if we need the extra subfolder at all. Maybe that would be a better option, actually:

materials/
└── django_markdown/
    ├── django_markdown/
    ├── django_markdown_app/
    ├── manage.py
    ├── README.md
    └── requirements.txt

[robalford]

I added that top level django-markdown folder based on the instructions above: 'New files should go into a top-level subfolder, named after the article slug. For example: my-awesome-article'.

But I think since I used an underscore in the project name in the tutorial, django_markdown, I will just move the readme file up to the the top level alongside the Django project folder to be consistent. It looks like some of the other Django projects in here are done this way.

[bzaczynski]

Probably need to run isort on your codebase to ensure consistent import statement ordering, which complies with PEP 8.