Django model naming conventions
Depending on the structure of other parts of your code, you could use the name of the Django app, a package, or a module to further scope the names.
I have a pretty stupid question about model naming conventions in Django.
Imagine a farmstead which has buildings which have rooms.
Farmstead --> Buildings --> Rooms
With Farmstead it is ok, let's call it a Farmstead. Next one: Building or FarmsteadBuilding? BuildingRoom, Room or FarmsteadBuildingRoom?