Virtual DOM

Accessibility (often abbreviated a11y) is the practice of designing and building websites and apps so they can be used by everyone, including people with visual, motor, auditory, or cognitive disabilities. This involves proper semantic markup, keyboard navigation support, sufficient color contrast, and screen reader compatibility. Beyond being an ethical responsibility, accessibility is increasingly a legal requirement in many jurisdictions.

A canary release is a deployment strategy where a new version is gradually rolled out to a small subset of users before reaching the full audience. Automated monitoring compares error rates, latency, and key metrics between the canary and the stable version. If the canary performs well, traffic is incrementally shifted; if anomalies are detected, the release is automatically rolled back, minimizing the blast radius of potential issues.

Progressive enhancement is a web development strategy that starts with a baseline of functional HTML content accessible to all browsers, then layers on CSS styling and JavaScript interactivity for more capable environments. This approach ensures that core functionality works everywhere, while users with modern browsers get a richer experience. It contrasts with graceful degradation, which starts with the full experience and tries to handle failures.

A task runner is a tool that automates repetitive development tasks like compiling code, running tests, minifying assets, and restarting servers. Early web task runners like Grunt and Gulp defined workflows as JavaScript code, while modern approaches use npm scripts, Turborepo, or Nx for monorepo-aware task orchestration. Task runners form the foundation of local development automation, ensuring every team member runs tasks consistently.

Optimistic UI is a pattern where the interface immediately reflects the expected result of a user action before the server confirms it. For example, a "like" button instantly shows the liked state while the API request happens in the background. This makes the app feel significantly faster and more responsive. If the server request fails, the UI rolls back to the previous state and notifies the user.

CI/CD (Continuous Integration / Continuous Deployment) is a set of practices that automate building, testing, and deploying code every time a developer pushes changes. Continuous Integration merges code into a shared branch frequently and runs automated tests, while Continuous Deployment automatically releases validated changes to production. Together they form the backbone of modern software delivery, reducing manual errors and accelerating release cycles.