A maintenance studio for the frontend you inherit, the migration you must justify and the service someone else will maintain.
The course#
One publication. Then a harder domain.#
The interview reader begins as a small Vue 2 interface. Its articles need an editorial desk, so you rebuild the management side in Vue 3. Finally, a fictional consultation service asks whether those architecture decisions survive a different domain: typed records, constrained transitions and failure that cannot be mistaken for success.
The question stays the same: where does truth live, who can change it, and what would make a change safe? This is a course about the work between tutorials: inherited conventions, version boundaries and handing a system to another developer.
What you need before arriving#
You should be comfortable writing HTML and CSS, JavaScript functions and arrays, DOM events, Git commits and basic Node / npm or pnpm commands. Responsive design, fetch and REST familiarity help, but request handling is taught here. We do not reteach JavaScript from scratch.
Try this entry check: render three records from an array, filter them from a labelled input, and commit the result. If that requires a full tutorial, revise those foundations before starting the first week.
What you will be able to do#
- Explain Vue reactivity and build an interface whose output follows its state.
- Design reusable components with explicit data and event contracts.
- Model SPA navigation with routes, parameters, guards and recovery paths.
- Choose local state, Vuex or Pinia according to ownership.
- Explain architectural differences between Vue 2 and Vue 3 without treating a rewrite as automatic improvement.
- Organise Vue 3 logic with Composition API.
- Use TypeScript to make domain assumptions and component boundaries explicit.
- Design shared request, authentication and error-handling layers.
- Test important state transitions and component behaviour.
- Leave a medium-sized frontend that another developer can understand and change.
How a teaching week works#
Read the Monday lecture and its deck, then attempt its concrete failure case. The Friday studio is a two-hour build and review session. Budget another five hours for preparation, independent work and your assessment project; this is a course planning expectation, not a separate assessed attendance quota.
Keep an ownership diagram and a migration ledger. The diagram changes as the application grows; the ledger records behaviour to preserve, APIs to change and dependencies to retire. Bring both to reviews.
The legacy boundary#
Vue 2 reached end of life on 31 December 2023. We use its archived documentation to learn maintenance and migration, not to recommend it for new production services. The second half uses Vue 3. Version families are separated on the resources page.
How your work is assessed#
Three practical projects carry the course. The reader establishes a complete Vue 2 application; the dashboard tests modern JavaScript architecture; the consultation service tests typed models, failure handling and handover. There is no mid-semester or final exam. See assessment dates and weights.