In corporate website projects, many disputes late in the process arise not from design quality but from an initial contract that vaguely promises to “complete website design and development” without defining a clear deliverable asset list. Clients expect their own technical team to be able to edit pages and add campaign sections after completion, only to receive minified production code they cannot readily edit or design files with missing fonts.
To protect a company's long-term control over its digital assets, JVDS uses a standardized four-part deliverables checklist for integrated website projects:
1. Visual and interaction design assets (Design Deliverables)
| Deliverable | File format | Contents and acceptance criteria |
|---|---|---|
| Complete high-fidelity design source files | .fig (Figma) or .sketch |
All approved desktop (1440px/1920px) and mobile (375px) pages, with consistent layer names and clear grouping |
| Website UI design system and component library | Figma component pages + PDF guidelines | Color variables (primary, secondary, neutral, and status colors), Chinese and English typography hierarchies, grid and spacing guidelines, and multi-state button, form, and card components (default, hover, pressed, disabled, and error) |
| Responsive breakpoints and interaction notes | Prototype link + annotated documentation | Navigation expansion logic, list filter states, modal feedback, empty states, and 404 page design notes |
| Exported images and vector icons | .svg / .webp / .png |
Losslessly compressed page images, individually exported SVG vector icons, and a favicon package in multiple sizes |
2. Copyright and third-party asset documentation (Licensing & Assets)
A font or image infringement notice is one of the last things a business wants after launching its website. A proper handover package must include a third-party asset licensing register specifying, item by item, the licensed commercial fonts used, stock-image purchase IDs (or the company's own photography library), and open-source icon libraries, such as Lucide or Remix Icon under the MIT license. This makes commercial-use boundaries clear and avoids hidden licensing issues.
3. Complete frontend and backend source code and database (Source Code & Database)
- A complete, unobfuscated project source package: Hand over a full code package or Git repository containing the source directory structure, configuration files, dependency manifests such as
package.json/composer.json, and build scripts. Never provide only compiled, minified static output. - Initial database schema and data backup: Provide complete SQL schema files and a backup of the initial launch data, so the company can restore the entire website in any standard server environment.
4. Deployment, operations, and CMS documentation (Documentation)
Include a Server Environment Configuration and Deployment Guide covering Nginx/Apache URL rewrite rules, SSL certificate renewal, and required PHP/Node versions. Also provide an illustrated CMS Daily Maintenance Manual showing marketing staff how to publish articles, update case studies, edit page title, description, and keyword metadata, and review inquiry records themselves.
