Foundations
How the web works, the terminal, Git and the first two languages.
- The web from the ground up40 h
- CSS that holds its shape40 h
- Programming with JavaScript42 h
Curriculum
12 units, 500 hours, six things you'll ship
One curriculum for both bootcamps. Full-time covers a unit a week, part-time a unit a fortnight. Pick your start date below and every week gets its real dates.
- HTML
- CSS
- JavaScript
- TypeScript
- Node
- SQL
- Git
- Testing
- Accessibility
- Deployment
You'd graduate on Fri, 9 April 2027
Apply for this cohort 11 Jan 9 Apr
- Foundations
- Front end
- Back end
- Product
- School break
-
Week 1 11 Jan – 15 Jan The web from the ground up Foundations 40 h a week
Topics
- How a browser loads a page
- Semantic HTML
- The terminal and your editor
- Git: commit, branch, push
What you build
A personal page, written from a blank file and published on day four.
Study time
40 hours in total, in one week
First pull request reviewed by a mentor
-
Week 2 18 Jan – 22 Jan CSS that holds its shape Foundations 40 h a week
Topics
- The box model and flow
- Flexbox and grid
- Responsive layout
- Design tokens and custom properties
What you build
A three-page site for a local business, rebuilt from a printed design.
Study time
40 hours in total, in one week
-
Week 3 25 Jan – 29 Jan Programming with JavaScript Foundations 42 h a week
Topics
- Values, functions and control flow
- Arrays and objects
- Debugging in the browser
- Writing your first tests
What you build
A command-line quiz and a set of 30 small exercises with passing tests.
Study time
42 hours in total, in one week
Foundations check: a 90-minute paired coding task
-
Week 4 1 Feb – 5 Feb The DOM and the event loop Front end 42 h a week
Topics
- Selecting and changing the page
- Events and forms
- Promises and async/await
- Fetching data from an API
What you build
A bus-times board that reads a public timetable feed and refreshes itself.
Study time
42 hours in total, in one week
-
Week 5 8 Feb – 12 Feb Components and state Front end 42 h a week
Topics
- Breaking a UI into components
- State and props
- Routing
- TypeScript basics
What you build
A habit tracker with filters, saved state and three routes.
Study time
42 hours in total, in one week
-
Week 6 15 Feb – 19 Feb Accessible, fast interfaces Front end 40 h a week
Topics
- Keyboard and screen-reader testing
- Colour and contrast
- Images, fonts and performance budgets
- Deploying a front end
What you build
Your habit tracker, audited and fixed until it passes an accessibility review.
Study time
40 hours in total, in one week
Front-end project demo to the cohort
-
Week 7 22 Feb – 26 Feb Servers and APIs Back end 42 h a week
Topics
- HTTP in depth
- Building a REST API with Node
- Validation and error handling
- Environment variables and secrets
What you build
An API for a lost-property office: report, search and claim items.
Study time
42 hours in total, in one week
-
Week 8 1 Mar – 5 Mar Databases Back end 42 h a week
Topics
- Relational modelling
- SQL by hand
- Migrations and an ORM
- Indexes and slow queries
What you build
The lost-property API on a real database, with seed data and migrations.
Study time
42 hours in total, in one week
-
Week 9 8 Mar – 12 Mar Auth, testing and shipping Back end 44 h a week
Topics
- Sessions, passwords and roles
- Integration and end-to-end tests
- Continuous integration
- Logging and monitoring
What you build
A full-stack app with sign-in, a test suite that runs on every push, and a live URL.
Study time
44 hours in total, in one week
Full-stack checkpoint: code review with a working developer
-
Week 10 15 Mar – 19 Mar Team project: plan and build Product 44 h a week
Topics
- Working from a brief with a real client
- Tickets, stand-ups and pull requests
- Pairing and code review
- Scope and trade-offs
What you build
Sprint one of a product for a Southampton charity or small business, in a team of four.
Study time
44 hours in total, in one week
-
Week 11 22 Mar – 26 Mar Team project: ship it Product 44 h a week
Topics
- User testing
- Fixing what testing found
- Writing a README and handover notes
- Presenting technical work
What you build
The team product, live, handed over to the client with documentation.
Study time
44 hours in total, in one week
Client sign-off
-
Week 12 5 Apr – 9 Apr Portfolio, interviews and demo day Product 38 h a week
Topics
- A portfolio that shows your thinking
- CV and LinkedIn review
- Technical interview practice
- Salary and offers
What you build
Your portfolio site with three projects written up, and a five-minute demo-day talk.
Study time
38 hours in total, in one week
Demo day in front of local employers
Four phases, each ending with something you can show
Front end
Interfaces people can use: layout, state, data from APIs, accessibility.
- The DOM and the event loop42 h
- Components and state42 h
- Accessible, fast interfaces40 h
Back end
Servers, databases, authentication and tests you can trust.
- Servers and APIs42 h
- Databases42 h
- Auth, testing and shipping44 h
Product
A team project shipped to real users, then the job search.
- Team project: plan and build44 h
- Team project: ship it44 h
- Portfolio, interviews and demo day38 h
Checkpoints a mentor signs off
You do not move on by attendance. At each of these, a mentor reviews your work with you and either signs it off or books a catch-up slot the following week.
- First pull request reviewed by a mentorThe web from the ground up
- Foundations check: a 90-minute paired coding taskProgramming with JavaScript
- Front-end project demo to the cohortAccessible, fast interfaces
- Full-stack checkpoint: code review with a working developerAuth, testing and shipping
- Client sign-offTeam project: ship it
- Demo day in front of local employersPortfolio, interviews and demo day
Want it on paper?
The syllabus PDF has every topic, the reading list and a sample week timetable for both formats.