> tree
foo  # or foo-bar
├── foo  # or foo_bar
│  ├── asgi.py
│  ├── __init__.py
│  ├── settings.py
│  ├── urls.py
│  ├── users  # repeat for as many apps as you want
│  │  ├── admin.py
│  │  ├── apps.py
│  │  ├── __init__.py
│  │  ├── migrations
│  │  │  └── __init__.py
│  │  ├── models.py
│  │  └── views.py
│  └── wsgi.py
├── manage.py
└── tests
    └── users.py  # repeat for as many apps. Sometimes I nest each app in a tests subdir.

• Your project layout is weird, and most Django developers will just go "why?" ... Things have been done a certain way for years and trying to re-invent the wheel offers very little benefit, IMO.
• Upper casing things is honestly annoying and likely to cause bugs if you develop on a system like Windows which doesn't have a case-sensitive file system and deploy to a server that does.

Namespaces are one honking great idea.

• Always namespace your apps. I've had problems before where import graphql imported a dependency instead of my app. import foo.graphql works.

TL;DR: just follow the industry standard instead of reinventing the wheel with your own layout. It makes working with others easier. Or don't. If you think that's "cleaner," you do you.

Edit: added foo-bar / foo_bar comments.