SLOP2797 · Undergraduate level 2Semester 1 · 202722 February 2027 — 28 May 2027

Frontend maintenance studio

Vue in the Wild

From Legacy Vue 2 to Typed Vue 3 Service Apps

You inherited the frontend.
Now make it worth inheriting.

Explore the twelve weeks Is this for me?
One question, three applications
01 / The readerVue 2Who owns state?
02 / The editorial deskVue 3What survives migration?
03 / The consultationVue + TSWhat makes change safe?

Components → shared boundaries → typed contracts.
The application grows. The ownership must stay legible.

The semester, at a glance

Every new layer earns its place.

  1. Weeks 01–07

    Inherit the reader.

    Vue 2 · Router · Vuex

    A saved flag becomes a mobile article app. Learn reactivity, component contracts and where shared state belongs.

  2. Weeks 08–09

    Move the architecture.

    Vue 3 · Composition API · Pinia

    Keep the behaviour, change the boundaries. Build the editorial desk for the same publication.

  3. Weeks 10–12

    Make change safer.

    TypeScript · Typed Vue · Tests

    Transfer the architecture to a fictional consultation service. Model impossible states, failure and the handover.

Bring JavaScript. Leave a handover.

Inherit a Vue 2 article app, rebuild its editorial desk in Vue 3, then carry the architecture into a typed consultation service. A frontend maintenance studio for developers who already know HTML, CSS and JavaScript.

Expect a weekly build, a concrete failure to diagnose and a review with another developer. Vue 2 is studied as an archived maintenance environment; the course deliberately moves into modern Vue.

See the three project briefs Open the workbench