From my notes

From my notes

Questions and flashcards written from your own study notes, each linking back to the note it came from, with a fact check of every note. Questions from your Important note are marked and trained first.

This section turns your notes into practice. The current set was written from scratch on 3 October 2026 from all of your notes; the first set was retired because you had learned it. Every question card has a My notes link to the notes it came from. Questions from your Important note carry an Important badge, lead every Smart training session, and can be drilled on their own with Important only in Train.

Know

  • Training: Train only the important ones, or open Train, press Only next to the Personal track and keep Smart order: due questions first, then unseen ones, with the important ones leading each group.
  • From a note: every notes page has a "questions from these notes" button that starts a session with exactly those questions.
  • Flashcards: the "Be able to say" blocks on these pages join the Flashcards deck; the Most important page has the most.
  • Adding more: keep writing notes filed under the study page you are reading, then ask for the next batch. Questions go into content/questions/my-notes.yml with a notes field naming their folder, and important: true when they come from the Important note.

How it works

Each question takes something you wrote down and asks it back from a different angle than your notes do: predicting output, finding the bug, choosing between two designs, or explaining it to a colleague. Where a note and the documentation disagree, the answer follows the documentation and says "your note says…", and the page for that topic lists the correction under Fact check of your notes.

Gotcha· Retired questions keep their history

Progress is stored per question id, so the first set (my-notes-001 to my-notes-064) was removed without reusing its ids. Your old grades stay in your data but no longer count anywhere, and the new questions start fresh.

Be able to say

Be able to say· Summarise how Vue turns a state change into a DOM update.

"A reactive read inside a render function, computed or watcher is tracked: the reading effect is recorded against that object and property. A write triggers those effects. Inside the assignment, computeds are only marked dirty, sync watchers run, and the component's update job is queued. When the call stack is empty, the scheduler flushes in a microtask: default watchers, then onBeforeUpdate, the render and the DOM patch, then onUpdated and post watchers. So a hundred changes in one tick cause one render, and code that needs the new DOM awaits nextTick()."

Pages in this section

  1. 01Most importantQuestions and flashcards from your Important note — reactivity and the event loop, the track and trigger engine, ref versus reactive, computed caching, watchers and flush timing, and the app lifecycle for client rendering, SSR and hydration, updates and unmount. Every question here is marked important and trained first.
  2. 02Vue essentialsQuestions and flashcards from your notes on the Vue docs' Essentials chapter — the app instance and error handler, template expressions, directives and their parts, class and style bindings, conditional and list rendering, keys, event modifiers, forms, template refs and dynamic components — with a fact check of the notes.
  3. 03Vue components in depthQuestions and flashcards from your notes on the Vue docs' Components In-Depth chapter — compiler macros, prop naming and read-only props, local drafts of props, event arguments, several v-models, v-model modifiers, defineModel and its pre-3.4 equivalent, fallthrough attributes, slots and dynamic scoped slots, provide/inject per subtree and async components — with a fact check of the notes.
  4. 04ReusabilityQuestions and flashcards from your notes on the Vue docs' Reusability chapter — composables with shared and per-caller state, conventions, toValue and MaybeRefOrGetter inputs, lifecycle hooks in composables, custom directives and their bindings, global directives, plugins and a small i18n plugin — with a fact check of the notes.
  5. 05Built-in componentsQuestions and flashcards from your notes on Vue's built-in components — what triggers a Transition and its classes, the move class of TransitionGroup, how KeepAlive caches instances and DOM, its hooks, max and include, Teleport's logical versus DOM hierarchy and deferred targets, and what Suspense waits for, with errors and Nuxt pages — with a fact check of the notes.
  6. 06Scaling upQuestions and flashcards from your notes on the Vue docs' Scaling Up chapter — why single-file components need compiling, how Vite's dev server works, code splitting, Vite 8 and Rolldown, Vue Router links, views, guards and reused instances, NuxtLink prefetching, global state on a server, test types, SSG versus SSR, and hydration mismatches from fetching and invalid HTML — with a fact check of the notes.
  7. 07Best practicesQuestions and flashcards from your notes on the Vue docs' Best Practices chapter — shallow reactivity for large data, v-once, v-memo, lazy components and virtual scrolling, focus after route changes, heading levels, landmarks and their roles, aria-hidden, labels and descriptions, the aria-labelledby spelling, URL injection and safe rich text — with a fact check of the notes.
  8. 08Nuxt under the hoodQuestions and flashcards from your Nuxt internals note — carrying values from build time to runtime, the start-up sequence from config loading to the bundles, module order and modules:done, config priority across layers, Nitro and h3, why h3 instead of Express, how a request reaches the Vue renderer, and deployment presets.

Your notes

Open in Notes

Nothing yet. Notes filed here show up on every page of this section.