Django Project : General Mumblings on Structure/Style
<project_configuration_root> /
Absolute root directory of the project
Store the project directory in here, as well as the project README file, project documentation, any design files, .gitignore, requirements.txt and any other high level files required by the project.
This is the project root.
Contains the “project_configuration_root”, media and static folders, templates and apps.
You could also have a libs directory for non-project specific apps/utilities etc.
1.3 project_configuration_root
Project settings, urlconf, wsgi etc. are placed in this directory.
2. Each app should have a specific purpose and focus on that; keep apps simple and reusable.
For example, you might have an Article app that focuses on articles.
A payments app to manage payment functionality and
an events app to support events in a project e.g. Free Coffee on Friday Night.
3. Apps should ideally have a single word name and where possible use a plural.
Keep in line with PEP8 for naming conventions.
When working with multiple environments e.g. PDN, DEV, Staging consider using multiple Requirements and Settings files,
with a base for each to provide a baseline.
5. Use South for Database migrations.
When new app is created, create the initial migration.
Then as you make changes or create new apps, create migrations including reverse migrations. data migrations.
Always follow PEP8; make use of add ons for your editor to automatically validate.
Use four spaces for indentation.
Don’t use camel case for vars and function names e.g.
myapp.get_articles() and not myapp.getArticles()
Use Pascal case for class names.
Keep views lightweight and simple; handling presentation logic, not business logic.
Keep business logic in models and if necessary in forms, but not in views.
pixelskylines
annaxmalina
snowghoul
dailybridgerton
tangentwithtanner