1 | | I propose that we make makes two changes to the `startproject` template: |
2 | | |
3 | | * instead of putting configuration files such as `settings.py`, `wsgi.py`, and the root `urls.py` in `my_project/my_project`, use `my_project/config` |
4 | | * start the project with a custom User model app, `users` |
5 | | |
6 | | Over the years, I've taught or tutored over 100 Djangonauts starting their first project. These two pain points came up the most frequently. Having to explain and distinguish between two directories with the same name is a constant pain point in the teaching process - "cd into my_project ... no, the other one!" |
7 | | |
8 | | It is sometimes better to show rather than tell, so following our own documentation and including a custom User model with the initial project template reinforces the best practice that we explicitly point out in the documentation. |
| 1 | I propose that we change the `startproject` template to put configuration files such as `settings.py`, `wsgi.py`, and the root `urls.py` in `my_project/config` instead of `my_project/my_project`. |
| 2 | |
| 3 | Over the years, I've taught or tutored over 100 Djangonauts starting their first project. Having to explain and distinguish between two directories with the same name is a constant pain point in the teaching process - "cd into my_project ... no, the other one!" |