Framework
also: frameworks
A ready-made foundation for building an app, with its own structure and rules. You fill in your parts, and it handles a lot of the common work.
A large body of reusable code that defines an application's structure and flow, and calls your code at the right moments (often called inversion of control). Examples include Next.js, Django, Rails and SwiftUI. Choosing one shapes the entire project.
If a library is a toolbox, a framework is the frame of a house, already standing. You add walls, paint and furniture, but the layout of the rooms is largely decided.
Your framework decides where files go and how things are done. Agents follow its conventions, so knowing which framework you're on helps you understand their choices. Switching later is a big job.
Since this project uses Django, I'll add the new page the Django way: a view, a URL entry and a template.
Stick to our framework's usual way of doing things. Don't add a second framework or a different way of organizing pages.
Thinking you can easily swap frameworks later. Your whole app is shaped around it, so changing frameworks usually means rebuilding large parts.