{"id":2490,"date":"2016-09-19T23:00:04","date_gmt":"2016-09-19T23:00:04","guid":{"rendered":"https:\/\/scope-development.com\/scopedesign\/2016\/09\/19\/web-designer-lingo-speed-hiring-designer\/"},"modified":"2026-11-05T18:48:14","modified_gmt":"2026-11-05T18:48:14","slug":"web-designer-lingo-master-essential-terminology","status":"publish","type":"post","link":"https:\/\/scopedesign.com\/cms\/web-designer-lingo-master-essential-terminology\/","title":{"rendered":"Web Designer Lingo: Master Essential Terminology Before Hiring Your Design Team"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Web design terminology is only useful if it helps you understand what you are buying, approving, owning, and verifying.<\/strong> Before <a href=\"https:\/\/scopedesign.com\/cms\/how-to-get-website-for-business-2025-guide\/\">you hire a web designer<\/a> or agency, you do not need to memorize a hundred technical terms. You do need to understand the words that define project scope, design deliverables, technical responsibilities, quality standards, account ownership, and handoff.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you are still sorting out what a web designer may actually be responsible for, start with our guide to <a href=\"https:\/\/scopedesign.com\/cms\/website-design-fundamentals-guide\/\">what website design includes<\/a>. This article has a narrower job: translating web designer lingo into the decisions a client has to make.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The web design terminology that matters most before you hire<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The most important web design terms fall into six practical stages: <strong>strategy, structure, interface, build, verification, and operation<\/strong>. A useful term should tell you something about what the team will produce, how you will review it, what standards apply, or who owns the result.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is why terms such as <em>scope<\/em>, <em>wireframe<\/em>, <em>responsive design<\/em>, <em>CMS<\/em>, <em>API<\/em>, <em>WCAG<\/em>, <em>QA<\/em>, <em>UAT<\/em>, <em>DNS<\/em>, and <em>handoff<\/em> usually matter more to a buyer than the name of a fashionable JavaScript framework.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Use the Scope Design Definition \u2192 Deliverable \u2192 Decision test<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When a proposal, designer, or developer uses jargon, run it through three questions:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Definition:<\/strong> What does the term mean in plain English?<\/li><li><strong>Deliverable:<\/strong> What page, file, behavior, account, test, document, or service proves that it is included?<\/li><li><strong>Decision:<\/strong> What do you need to approve, provide, own, budget for, or verify?<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a proposal may say the website will be <strong>responsive<\/strong>. The definition is straightforward: the layout should adapt to different screen sizes. The deliverable is not the word \u201cresponsive\u201d; it is the implemented page behavior across the agreed range of screens. The decision is what devices, breakpoints, browsers, and acceptance checks are actually in scope.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same rule exposes vague promises. \u201cSEO included,\u201d \u201caccessible website,\u201d \u201coptimized performance,\u201d and \u201congoing support\u201d sound reassuring, but each phrase is still ambiguous until the provider explains the work, evidence, boundaries, and owner.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1600\" height=\"900\" src=\"https:\/\/scopedesign.com\/cms\/wp-content\/uploads\/2016\/09\/project-terms-map.jpg\" alt=\"A web project map connects strategy and scope, structure, interface, build, verification, and operation to the client decision at each stage.\" class=\"wp-image-17703\" srcset=\"https:\/\/scopedesign.com\/cms\/wp-content\/uploads\/2016\/09\/project-terms-map.jpg 1600w, https:\/\/scopedesign.com\/cms\/wp-content\/uploads\/2016\/09\/project-terms-map-300x169.jpg 300w, https:\/\/scopedesign.com\/cms\/wp-content\/uploads\/2016\/09\/project-terms-map-1024x576.jpg 1024w, https:\/\/scopedesign.com\/cms\/wp-content\/uploads\/2016\/09\/project-terms-map-768x432.jpg 768w, https:\/\/scopedesign.com\/cms\/wp-content\/uploads\/2016\/09\/project-terms-map-1536x864.jpg 1536w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Web design terms at a glance<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Project stage<\/th><th>Terms you may hear<\/th><th>What those terms should clarify<\/th><\/tr><\/thead><tbody><tr><td>Strategy<\/td><td>Discovery, requirements, scope, deliverable, dependency, acceptance criteria<\/td><td>What problem is being solved and what is included<\/td><\/tr><tr><td>Structure<\/td><td>Sitemap, information architecture, user journey, content hierarchy<\/td><td>What pages and paths people need<\/td><\/tr><tr><td>Interface<\/td><td>UX, UI, wireframe, mockup, prototype, component, responsive design<\/td><td>What you are reviewing and approving before or during build<\/td><\/tr><tr><td>Build<\/td><td>Frontend, backend, CMS, template, API, integration, staging<\/td><td>What system makes the approved experience work<\/td><\/tr><tr><td>Verification<\/td><td>WCAG, QA, UAT, cross-browser testing, Core Web Vitals, redirects<\/td><td>How the team will prove the implementation meets the agreed requirements<\/td><\/tr><tr><td>Operation<\/td><td>Domain, DNS, hosting, admin account, license, backup, maintenance, handoff<\/td><td>Who controls the website and what happens after launch<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Strategy and scope terminology<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Discovery<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Discovery<\/strong> is the work used to understand the business problem, audience, current website, constraints, evidence, content, technology, and success criteria before important design decisions are locked in. Depending on the project, discovery might include stakeholder interviews, analytics review, content inventory, technical review, audience research, competitive context, or workshop sessions.<\/p>\n\n\n<p class=\"wp-block-paragraph\"><strong>Ask:<\/strong> What exactly happens during discovery, who participates, and what decisions or documents come out of it?<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Requirements<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Requirements<\/strong> describe what the website must do or support. \u201cWe need a contact page\u201d is a page request. \u201cQualified prospects must be able to choose a service, submit the correct project information, and route the inquiry to the right team\u201d is closer to a functional requirement.<\/p>\n\n\n<p class=\"wp-block-paragraph\">Requirements can cover content, functionality, integrations, accessibility, performance, security, reporting, legal constraints, and operational needs. They create a basis for design and acceptance instead of leaving everyone to infer the job from a page count.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scope<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Scope<\/strong> is the agreed boundary of the project. It should make the included work, exclusions, assumptions, responsibilities, schedule, and change process understandable. Scope is not the same thing as a feature list. Two \u201c10-page websites\u201d can represent radically different amounts of strategy, copywriting, design, development, migration, testing, training, and support.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Deliverable<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>deliverable<\/strong> is a concrete output the project is supposed to produce. Examples include a sitemap, copy deck, wireframe, approved design, component library, working form, CMS template, redirect map, training session, or handoff document.<\/p>\n\n\n<p class=\"wp-block-paragraph\">If a proposal uses a broad term such as \u201cSEO,\u201d \u201caccessibility,\u201d or \u201coptimization,\u201d ask what deliverables or checks are included under that label.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>dependency<\/strong> is something another task relies on. Final page design may depend on approved copy. A payment integration may depend on credentials from your processor. Launch may depend on DNS access. Naming dependencies early makes schedule discussions more realistic.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Change request<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>change request<\/strong> is a documented change to agreed scope, requirements, deliverables, or assumptions. It should explain what changed and whether the change affects cost, schedule, testing, or other work. A good change process protects both sides from silently turning a defined project into an unlimited one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Acceptance criteria<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Acceptance criteria<\/strong> describe the conditions that must be true for a deliverable or feature to be accepted. \u201cBuild a form\u201d is vague. \u201cThe form validates required fields, sends the submission to the agreed destination, displays a confirmation, records the event in analytics, and works in the supported browsers\u201d is testable.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Structure and user-flow terminology<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Sitemap<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>sitemap<\/strong> in the planning sense is a map of the website\u2019s pages and hierarchy. It helps the team decide what content exists, how pages relate, and what belongs in navigation. Do not confuse this planning artifact with an XML sitemap used by search engines.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Information architecture (IA)<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Information architecture<\/strong> is the way information is organized, labeled, grouped, and connected so people can find and understand it. IA affects navigation, page hierarchy, labels, content relationships, and the paths users take through the site.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">User journey<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>user journey<\/strong> describes the steps a person may take while trying to accomplish a goal. For a service business, one journey might be: understand the service, verify fit, review proof, compare options, ask a question, and submit an inquiry. The point is not to draw a pretty diagram. It is to reveal what a visitor needs at each decision.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Design and approval terminology<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">UX and UI<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>UX<\/strong> means user experience. It deals with how understandable, usable, efficient, and appropriate the experience is for the person trying to accomplish a task. <strong>UI<\/strong> means user interface. It covers the interface people see and interact with, including controls, visual hierarchy, states, components, spacing, typography, and presentation.<\/p>\n\n\n<p class=\"wp-block-paragraph\">They overlap, but they are not interchangeable. A beautiful interface can still produce a poor experience if users cannot find the right information or complete an important task. If you need to diagnose those problems, our <a href=\"https:\/\/scopedesign.com\/cms\/design-that-converts-ux-principles-user-centered-strategies\/\">UX diagnosis guide<\/a> goes deeper.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Wireframe<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>wireframe<\/strong> is a simplified representation of page structure and priority. It usually focuses on layout, content hierarchy, and interaction rather than final typography, color, imagery, and polish. Its job is to make structural decisions cheaper to discuss before visual detail distracts everyone.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mockup<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>mockup<\/strong> is a more visually complete representation of the intended interface. It may show real typography, colors, imagery, components, spacing, and brand treatment, but it is not necessarily interactive or implemented.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prototype<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>prototype<\/strong> simulates some part of the experience so flows and interactions can be evaluated before the full system exists. A prototype can be simple or high fidelity. It is still a model. <strong>Approving a prototype or mockup is not the same as accepting a functioning website.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Design system and component<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>component<\/strong> is a reusable interface element or pattern, such as a button, card, form field, testimonial block, or navigation item. A <strong>design system<\/strong> organizes reusable components together with rules, tokens, patterns, and guidance so the interface can stay coherent as it grows.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Responsive design, mobile-first, and breakpoint<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong><a href=\"https:\/\/scopedesign.com\/cms\/responsive-web-design\/\">Responsive web design<\/a><\/strong> is an approach that allows layouts and content to adapt across different screen sizes and device conditions. <strong>Mobile-first<\/strong> is a way of designing or coding from a smaller-screen baseline and progressively adapting for larger screens. A <strong>breakpoint<\/strong> is a condition, commonly based on viewport width, where layout behavior changes.<\/p>\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Learn_web_development\/Core\/CSS_layout\/Responsive_Design\" target=\"_blank\" rel=\"noopener\">MDN\u2019s responsive design guidance<\/a> treats responsive design as an approach rather than a single device checklist. For a client, the important question is what responsive behavior will be tested and accepted, not whether the proposal contains the phrase \u201cmobile-friendly.\u201d<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Development and technology terminology<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Frontend and backend<\/h3>\n\n\n<p class=\"wp-block-paragraph\">The <strong>frontend<\/strong> is the part of the website delivered to and interacted with by the user, including the rendered interface and browser-side behavior. The <strong>backend<\/strong> is the server-side or administrative layer that may handle data, business logic, authentication, content, integrations, or other services behind the interface.<\/p>\n\n\n<p class=\"wp-block-paragraph\">On many business websites, the boundary is less important to a client than the responsibility: who owns the interface, who owns data and integrations, and who fixes a problem when the two do not work together?<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">CMS<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>content management system (CMS)<\/strong> is software used to manage website content. WordPress is a CMS. A CMS can make editing easier, but \u201cCMS included\u201d does not tell you how much control you will have, which content types are editable, whether custom fields exist, or how portable the site is.<\/p>\n\n\n<p class=\"wp-block-paragraph\"><strong>Ask:<\/strong> What can our team edit safely? Which roles will we have? Who holds the administrator account? What training and documentation are included?<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Template, theme, and component<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>template<\/strong> controls the structure for a type of page or content. A <strong>theme<\/strong> usually refers to a larger presentation layer or package of templates, styles, and behavior, especially in systems such as WordPress. A site can use a theme and still include original design; a theme can also impose real constraints. The useful question is what is custom, what is reusable, and what the licensing or maintenance implications are.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">API and integration<\/h3>\n\n\n<p class=\"wp-block-paragraph\">An <strong>API<\/strong>, or application programming interface, is an interface that lets software interact with another system. An <strong>integration<\/strong> is the implemented connection that uses an API, webhook, feed, plugin, file exchange, or another method to move data or trigger behavior between systems. <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Glossary\/API\" target=\"_blank\" rel=\"noopener\">MDN describes an API as the interface or contract that exposes features for software interaction<\/a>.<\/p>\n\n\n<p class=\"wp-block-paragraph\">An \u201cAPI integration\u201d line item should identify the systems involved, data or actions exchanged, authentication responsibilities, failure behavior, testing, and who maintains the connection when one platform changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Staging and production<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Staging<\/strong> is a non-public or controlled environment used to review and test work before it affects the live website. <strong>Production<\/strong> is the live environment serving real users. Ask how changes move from staging to production, what gets backed up, and what the rollback plan is if a launch causes a problem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Domain, DNS, and hosting<\/h3>\n\n\n<p class=\"wp-block-paragraph\">Your <strong>domain name<\/strong> is the human-readable address people use to reach the site. <strong>DNS<\/strong> is the system of records that directs that domain to services such as the website and email. <strong>Hosting<\/strong> is the infrastructure where the website application, files, or services run.<\/p>\n\n\n<p class=\"wp-block-paragraph\">These are related but separate. A provider can host your website without owning your domain. Your business should know who controls the registrar account, DNS records, hosting account, billing, recovery email, and multi-factor authentication.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SSL certificate, HTTPS, and TLS<\/h3>\n\n\n<p class=\"wp-block-paragraph\">You will still hear people say <strong>SSL certificate<\/strong>, but modern HTTPS uses <strong>TLS<\/strong>. <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Glossary\/HTTPS\" target=\"_blank\" rel=\"noopener\">HTTPS is HTTP carried over a secure TLS connection<\/a>, and TLS is used to provide encryption, integrity, and server authentication. For a client, the practical concern is that HTTPS is correctly configured, renewed, monitored, and not broken by mixed content or bad redirects.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Quality, accessibility, and measurement terminology<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Accessibility and WCAG<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Web accessibility<\/strong> means designing and building digital experiences so people with disabilities can perceive, understand, navigate, and interact with them. <strong>WCAG<\/strong> is the Web Content Accessibility Guidelines published by W3C. <a href=\"https:\/\/www.w3.org\/TR\/WCAG22\/\" target=\"_blank\" rel=\"noopener\">WCAG 2.2 is a W3C Recommendation<\/a> and provides testable success criteria.<\/p>\n\n\n<p class=\"wp-block-paragraph\">If a proposal says \u201c<a href=\"https:\/\/scopedesign.com\/cms\/how-to-make-your-website-ada-compliant\/\">ADA compliant<\/a>\u201d or \u201cWCAG compliant,\u201d ask what standard and conformance target are being used, what pages or templates will be evaluated, what testing methods are included, who remediates failures, and what remains the client\u2019s responsibility for future content.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">QA and UAT<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Quality assurance (QA)<\/strong> is the team\u2019s process for checking whether the implementation works as intended and meets the agreed requirements. <strong>User acceptance testing (UAT)<\/strong> is the client or business-side verification that the system is acceptable for the intended real-world use before final acceptance or launch.<\/p>\n\n\n<p class=\"wp-block-paragraph\">They should not be treated as synonyms. QA asks whether the team built the thing correctly. UAT asks whether the delivered thing satisfies the agreed business use and acceptance criteria.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cross-browser and device testing<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Cross-browser testing<\/strong> checks behavior in the agreed browsers and versions. <strong>Device testing<\/strong> checks the experience across the screen sizes, input methods, and device conditions that matter to the project. \u201cWorks everywhere\u201d is not a responsible test plan. A scope should state the supported range and how important exceptions are handled.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core Web Vitals<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Core Web Vitals<\/strong> are Google\u2019s user-experience metrics for loading performance, responsiveness, and visual stability. The current metrics are <strong>Largest Contentful Paint (LCP)<\/strong>, <strong>Interaction to Next Paint (INP)<\/strong>, and <strong>Cumulative Layout Shift (CLS)<\/strong>, as documented by <a href=\"https:\/\/web.dev\/articles\/vitals\" target=\"_blank\" rel=\"noopener\">web.dev<\/a>.<\/p>\n\n\n<p class=\"wp-block-paragraph\">If performance is included in a project, ask what will be measured, under what conditions, and whether the promise concerns lab testing, real-user data, or a specific threshold. A score without context can be as misleading as a buzzword.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SEO foundations<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>SEO foundations<\/strong> usually refers to the technical and content setup that helps search engines discover, interpret, and present the site correctly. It can include crawl\/index controls, titles and descriptions, canonical URLs, redirects, internal links, structured data, XML sitemaps, and migration checks. It is not the same as an indefinite promise to rank for competitive queries.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Redirect<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>redirect<\/strong> sends an old URL to another URL. Redirect planning matters during redesigns and migrations because changing paths without a plan can break links, bookmarks, referrals, and search signals. If URLs will change, the proposal should say who inventories old URLs, creates the redirect map, implements it, and verifies the result.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Analytics, event, and conversion<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Analytics<\/strong> is the measurement system used to understand activity on the website. An <strong>event<\/strong> is a recorded interaction or occurrence, such as a form submission, download, purchase, or qualified button click. A <strong>conversion<\/strong> is an action the business has decided represents meaningful progress or value.<\/p>\n\n\n<p class=\"wp-block-paragraph\">\u201cAnalytics installed\u201d is not a measurement strategy. Ask which outcomes are being tracked, who owns the account, how consent requirements are handled, and what the team will verify before handoff.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ownership and handoff terminology<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is where apparently small words can turn into expensive surprises. Our guide to <a href=\"https:\/\/scopedesign.com\/cms\/complete-guide-working-with-web-design-company\/\">working with a web design company<\/a> covers the broader client-agency responsibility model. At minimum, understand the terms below before the final invoice or launch week.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Administrator account<\/h3>\n\n\n<p class=\"wp-block-paragraph\">An <strong>administrator account<\/strong> has elevated control over a system. Your business should know which systems require administrative access and whether a company-controlled account will exist for the domain registrar, DNS, hosting, CMS, analytics, search tools, payment services, email delivery, and other critical integrations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">License<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>license<\/strong> grants permission to use software, fonts, images, plugins, themes, code, or other intellectual property under specific terms. \u201cIncluded\u201d does not always mean \u201cowned forever.\u201d Ask which licenses are recurring, transferable, agency-owned, client-owned, or replaced if the relationship ends.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Source files and repository<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Source files<\/strong> are the editable originals used to create the delivered work. A <strong>repository<\/strong> is a system, commonly Git-based for code, that stores and tracks source changes. Not every simple website needs a client-managed code repository, but every client should understand what files and source materials exist, where they live, and what is transferred at handoff.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Backup and restore<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A <strong>backup<\/strong> is a recoverable copy of website data or files. A <strong>restore<\/strong> is the tested process of returning the system to a usable state from that backup. Ask what is backed up, how often, how long copies are retained, where they are stored, and who is responsible for restoration.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Maintenance and support<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Maintenance<\/strong> is planned work that keeps the website healthy over time, such as updates, backups, security work, compatibility checks, performance monitoring, and content-system care. <strong>Support<\/strong> usually refers to help when questions, incidents, or change requests occur. The scope should define what is included, what is billable, response expectations, and who owns urgent issues.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Handoff<\/h3>\n\n\n<p class=\"wp-block-paragraph\"><strong>Handoff<\/strong> is the transfer of the website, accounts, credentials, documentation, training, files, licenses, and operational responsibility at the end of a project or relationship. A good handoff is not \u201chere is the login.\u201d It is a controlled transfer that makes clear what the client now owns and what the provider still manages.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Five web design terms people commonly confuse<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Terms<\/th><th>Plain-English difference<\/th><\/tr><\/thead><tbody><tr><td>Wireframe vs. mockup vs. prototype<\/td><td>A wireframe emphasizes structure, a mockup emphasizes visual design, and a prototype simulates interaction or flow.<\/td><\/tr><tr><td>Domain vs. DNS vs. hosting<\/td><td>The domain is the address, DNS directs the address to services, and hosting runs the website system.<\/td><\/tr><tr><td>Responsive vs. mobile-first<\/td><td>Responsive is the broader adaptive approach; mobile-first starts design or implementation from smaller screens and expands upward.<\/td><\/tr><tr><td>UX vs. UI<\/td><td>UX concerns the quality of the experience and task flow; UI concerns the interface people see and operate.<\/td><\/tr><tr><td>QA vs. UAT<\/td><td>QA is the delivery team\u2019s quality verification; UAT is business-side acceptance of the delivered system for its intended use.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Terms that should be defined in the written scope<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Some terminology is too important to leave as sales-call shorthand. When you compare proposals, require the important promises to become written responsibilities. Our full guide to <a href=\"https:\/\/scopedesign.com\/cms\/how-to-choose-best-web-design-company-complete-guide\/\">choosing a web design company<\/a> covers vendor evaluation in detail. For terminology, focus on whether the scope defines these items clearly:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Deliverables and exclusions:<\/strong> what is included and what is not.<\/li><li><strong>Dependencies:<\/strong> what the client or a third party must provide and by when.<\/li><li><strong>Revisions and change requests:<\/strong> how feedback works and when added work changes cost or schedule.<\/li><li><strong>Acceptance criteria and UAT:<\/strong> how completion is judged.<\/li><li><strong>Browser and device support:<\/strong> what environments are tested.<\/li><li><strong>Accessibility target:<\/strong> what standard, conformance level, templates, and testing are included.<\/li><li><strong>Performance target:<\/strong> what metrics are measured and under what conditions.<\/li><li><strong>SEO and redirects:<\/strong> what migration or technical search work is actually included.<\/li><li><strong>Ownership and licensing:<\/strong> who controls accounts, source, content, software licenses, and third-party services.<\/li><li><strong>Handoff and training:<\/strong> what is transferred and how your team learns to operate it.<\/li><li><strong>Recurring costs and support:<\/strong> what continues after the project and what happens if the relationship ends.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A proposal does not become sophisticated because it uses sophisticated words. It becomes useful when important terms have enough definition that both sides can tell what will happen next.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Questions to ask when a designer uses jargon<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li>What does that term mean on <em>this<\/em> project?<\/li><li>What deliverable, behavior, account, or test proves it is included?<\/li><li>What do you need us to approve or provide?<\/li><li>Who owns this after the project ends?<\/li><li>How will we verify it before acceptance?<\/li><li>What is specifically excluded?<\/li><li>If a third-party tool changes or breaks, who is responsible?<\/li><li>Does this create a recurring license, hosting, maintenance, or support cost?<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Those questions are more useful than trying to impress a designer by repeating technical vocabulary. Good web professionals should be able to explain a decision without hiding behind terminology.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions about web design terminology<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What does web design terminology mean?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">Web design terminology is the vocabulary used to describe website strategy, structure, user experience, interface design, development, performance, testing, hosting, ownership, and maintenance. For a business owner, the useful terms are the ones that clarify what is being purchased, approved, tested, or handed over.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What web design terms should I know before hiring a designer?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">Start with scope, deliverable, dependency, acceptance criteria, sitemap, information architecture, UX, UI, wireframe, mockup, prototype, responsive design, CMS, API, staging, domain, DNS, hosting, WCAG, QA, UAT, Core Web Vitals, administrator account, license, maintenance, and handoff. You can learn tool-specific vocabulary later if your project actually needs it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between UX and UI?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">UX focuses on the quality of the user\u2019s experience, including comprehension, navigation, task flow, and usability. UI focuses on the interface people see and interact with, such as controls, typography, spacing, visual hierarchy, and component states. Strong website work usually requires the two to support each other.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between a wireframe, mockup, and prototype?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">A wireframe is mainly about structure and hierarchy. A mockup is a more complete visual representation. A prototype simulates some interaction or flow. None of those automatically proves the final built website works correctly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is a CMS the same thing as hosting?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">No. A CMS is software used to manage content. Hosting is the infrastructure that runs or serves the website. A WordPress website, for example, uses WordPress as its CMS while running on a hosting environment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need to know how to code before hiring a web designer?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">No. A client does not need to become a frontend or backend developer. You should understand enough terminology to ask what is included, what is custom, what can be edited, how the work will be tested, what you will own, and what responsibilities continue after launch.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does \u201cSSL certificate\u201d still mean the same thing?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">People commonly still say \u201cSSL certificate,\u201d but modern secure web connections use TLS. The practical requirement is a correctly configured HTTPS connection, a valid certificate, reliable renewal, and monitoring for security or redirect problems.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between QA and UAT?<\/h3>\n\n\n<p class=\"wp-block-paragraph\">QA is the delivery team\u2019s process for finding defects and checking the implementation against requirements. UAT is the client or business-side process for confirming that the delivered website is acceptable for its intended use. Both matter, and neither should be replaced by a quick visual review.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Know enough lingo to make better decisions, not to play designer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The goal of learning web designer lingo is not to micromanage the people you hire. It is to recognize when an important promise is specific enough to approve and when it still needs a definition.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use the <strong>Definition \u2192 Deliverable \u2192 Decision<\/strong> test whenever a proposal or project conversation becomes fuzzy. If a term cannot be connected to a concrete output, behavior, account, test, responsibility, or owner, keep asking questions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you want a web team that explains the work in business language and makes responsibilities explicit, <a href=\"https:\/\/scopedesign.com\/cms\/\">talk with Scope Design<\/a> about your website project.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn the web design terminology that actually affects a website project, including scope, UX, CMS, accessibility, performance, ownership, QA, and handoff. Use Scope Design\u2019s Definition \u2192 Deliverable \u2192 Decision test to turn jargon into practical buying and approval decisions.<\/p>\n","protected":false},"author":1,"featured_media":17702,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[19],"tags":[277,13,275,276,195],"class_list":["post-2490","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-website-solutions","tag-ux","tag-web-design","tag-web-design-terminology","tag-website-development","tag-website-planning"],"acf":{"scope_editorial_pick":false},"_links":{"self":[{"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/posts\/2490","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/comments?post=2490"}],"version-history":[{"count":0,"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/posts\/2490\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/media\/17702"}],"wp:attachment":[{"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/media?parent=2490"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/categories?post=2490"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scopedesign.com\/cms\/wp-json\/wp\/v2\/tags?post=2490"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}