Glossary
Website feedback, defined.
Plain-language definitions of the terms that come up in website feedback, design review, and design QA.
- AnnotationA single piece of feedback attached to a specific spot in the work under review: an element on a page, a region of an image, or a place in a PDF.
- Coding agentAn AI tool, such as Claude Code or Cursor, that reads a codebase and performs programming tasks from natural-language instructions.
- Design driftThe gradual divergence between the design file and the live product, as fixes, content changes, and quick patches accumulate in production.
- Design feedbackReactions and change requests on design work, from a client's gut feeling about a homepage to a designer flagging that the build does not match the mockup.
- Design handoffThe moment design work moves to development: the specs, assets, and intent a developer needs to build what was designed.
- Design QAThe step where the built product is checked against the design: colors, typography, spacing, and layout, before or shortly after release.
- Design reviewA structured look at design work by stakeholders, teammates, or clients, with the goal of approving it or listing what must change.
- Model Context Protocol (MCP)An open protocol that lets AI assistants and coding agents connect to external tools and data sources through a standard interface.
- Staging environmentA private copy of a website where changes are reviewed and tested before they reach the production site that visitors see.
- Visual feedbackFeedback given on top of the thing itself, like a pin on a live page or a marked-up screenshot, instead of describing it in words elsewhere.
- Visual regression testingAutomatically comparing screenshots of a site before and after a change, to catch unintended visual differences.
- Website annotationPlacing comments directly on a website's pages, anchored to specific elements, so feedback lives where the work is.
- Website feedbackComments, change requests, and bug reports collected about a website, ideally pinned to the exact element they are about instead of described in an email.
Because feedback shouldn’t be the hard part.
One link for your clients to review, one list for your team to resolve.