Techxeeria
Python and SQL through Django or Flask REST APIs into a React client, ending in a tested ecommerce build.
The full-stack syllabus divides cleanly into backend and frontend phases. Backend work uses Django: URL configuration routes a request to a view, the view reads and writes model instances through the ORM, and the response returns either as a server-rendered template or as JSON from a REST endpoint. Flask covers the same ground differently — it supplies URL routes and view functions with framework integration that is independent of Django's URLconf and ORM layer, so Django's URL configuration specifically does not appear in a Flask project. The Django overview describes the URLconf-to-view-to-model request cycle directly, making the distinction between template responses and API responses concrete.
Frontend work introduces HTML, CSS, and JavaScript before React, where components consume the REST endpoints the backend exposes. Named practice builds include a student manager, a Django library manager, a blog API, a React weather app, and a task manager. The final exercise combines React, Django, and SQL into a CRUD and authentication ecommerce application, then adds API and UI testing and a deployment step.
Suggested practice (grounded in the Django overview): implement a single object lookup twice — once returning a template, once returning JSON — then call the JSON version from a fetch in a React component. The two wiring decisions become directly comparable rather than abstract.
Further reading