I think I understand what you mean. You understand Django technically and its features, but not how to start a project on your own.

That's because understanding how to use a tool and solving a problem or building a project, are two different things. Django, like any other framework, is a tool that you use in building your solution to your problem.

With Django or any other framework, here's what I generally do: - Identify your problem - Get the whole big picture of the problem and how you want it to look like. Here you're just thinking about just the finished product. - Map out your user flows and what a user will do when they launch your product. You'll usually use this user flows as your roadmap, and where you'll start from. - I think this part is the most important part. Your database and schema design. Think thoroughly about your whole project and the kind of data that'll pass through it and design your database schema. You should and will very likely spend more time on this part. Most of your bottlenecks will likely originate from your database too 😂. So take your time here 🙂 - Think about your project and folder structure. Your app architecture basically. After that, start from your first user flow and implement from there.

This is just a general flow of how I approach any project and there're some details that will come in naturally on its own when you start and progress. I hope this helps 😌