Design Multiple Corporate Websites in One Day: Proven Workflow and System
Over the past six months the author handled dozens of corporate website projects, identified recurring design problems such as limited resources, high labor cost, lack of brand identity and poor user experience, and introduced a systematic workflow—including resource integration, component libraries, modular templates and a code‑generation tool—that enables the rapid production of multiple web designs within a single day.
Background
In the last half‑year I worked on dozens of corporate website requests. Each design‑to‑development review consumed a large amount of time, so I distilled a workflow that can generate multiple web designs in just one day.
Problems in Website Design
Many business lines, scarce resources – Simultaneous demands from multiple business units overload designers and hinder business understanding.
High labor cost – Limited design resources require repeated hand‑offs with developers, reducing efficiency.
No brand consistency – B‑end products lack a unified visual identity, resulting in a fragmented experience.
Poor user experience – Repetitive functional designs meet requirements but fail to deliver a friendly experience.
Breakthrough Approach
Analysis showed that over 50% of design content is duplicated across projects. The solution is to systematize this repeated work: build a design system, integrate resources, create standardized modules, and reverse‑engineer the modules back to product specifications, thereby improving design efficiency and reducing collaboration cost.
Workflow
The process follows four steps: Collect requirements → Integrate & categorize → Define components → Code implementation .
Step 1: Integrate Resources and Define Modules
Resources from different business lines are grouped into three categories: data middle‑platform, technology middle‑platform, and business middle‑platform. By classifying these, we identified more than 15 high‑frequency components such as Banner, Product Advantages, Cases, Information Flow, Partners, Contact Us, About Us, Usage Process, Feature Introduction, Device Display, Maps, etc.
Step 2: Module Sorting and Template Creation
Modules are further sorted by reuse rate, and corresponding templates are created. High‑reuse modules receive richer template variations.
Design Language
For B‑end products we adopt a "light‑neumorphism" style that emphasizes detail without overwhelming the content. Core visual keywords are technology , efficiency and simplicity . The color palette follows the Matrix system with a dominant blue and a range of light‑dark shades for flexibility.
Typography and color specifications are defined, and layouts use a grid system tailored to home‑page and inner‑page structures.
Icon Innovation
Icons are divided into three hierarchy levels for different scenarios. We introduced 3D icons for high‑priority modules (limited to four), glass‑ball icons that blend a frosted‑glass feel with geometric composition, and linear icons with subtle 3D depth for broad usage.
Three‑Dimensional Design
Banner modules are split into 3D and 2D styles. Commercial or public‑welfare sites use image‑based banners for clear messaging, while technical sites employ 3D banners to convey a sense of technology.
Actual Application
To date we have produced over 50 modules and more than 10 page templates. By codifying these assets into the "YunDa" web‑generation tool and integrating it into a middle‑platform, we now support multiple business lines, streamline the path from design to code, and provide a one‑stop solution that significantly boosts product development efficiency.
The next article will detail how designers translate product and interaction thinking into the "YunDa" tool.
Illustrative Images
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
