The Python outline spans over 36 days and covers topics such as expressions, variables, functions, modules, strings, conditionals, loops, lists, tuples, dictionaries, error handling, pip, linting, algorithm complexity analysis, classes and objects, Django, databases, the Django ORM, URL patterns, views, templates, and building a full-stack web application with server-side functionality using Python and Django. Students will work on extending HTML/CSS/JS projects with server-side functionality involving a database to persist and display user data.

1. Python Outline
Day 1, 2, 3:
- Intro
- Expressions & Types
- Variables
- Function Calls
- Modules
- User-Defined Functions
- Strings
- Comments
- Conditionals
Day 4:
- Loops
- Lists & Tuples
Day 5, 6:
- Dictionaries
- Error handling
Day 7:
- pip
- Linting
Day 8:
- Algorithm complexity analysis
(https://www.cs.cornell.edu/courses/cs1110/2020fa/lessons/lesson30/slides-30.pdf)
Day 9-14:
- Do at least 15 Codility tasks
- The purpose is to polish students' problem solving skills
Day 15, 16:
- Classes & Objects
Day 17:
- What is Django?
- Install Python and Django
- Create a Django project
- Create a Django app
- Models, routing, views, and templates
Day 18, 19:
- Django models
- Django fields
- Implement models and fields
- Django migrations
- Work with the Django admin
Day 20, 21:
- Intro to Databases
- What is SQL
- SQLLite GUI tool
Day 22:
- Python database API
Day 23, 24:
- Query data with the Django ORM
- Understand URL patterns
- Implement URL patterns
- Implement Django views
Day 25, 26, 27:

2. - Django templates
- Implement Django templates
- Structure templates
- Integrate CSS and JavaScript
- Resources and next steps
Day 28, 29, 30:
Revision
Day 31 to 36:
- Students will work on extending their HTML/CSS/JS projects (ideally in the same
groups) with server-side functionality. The server-side functionality must involve the
use of a database to persist data entered/generated by users during usage of the
website frontend. The persisted data should also be displayed, summarized and/or
graphically presented on the website frontend. An authentication system is not
required but is recommended in appropriate projects. Any forms should feature both
client-side and server-side validation.