Rulebase
Precise and credible, using real interfaces and restrained signal colors.
This is the original design with sample content, not YUNROU client work. Your website uses your own identity, copy and imagery.

A good fit for
- AI, fintech and B2B SaaS
- Products with several real workflows
- Teams needing product, resources and company content
Bring this material
Real UI, workflows, integrations, capability copy and verified proof.
This is guidance, not a quota. With less real content, we adjust the page scope instead of inventing work.
When to reconsider
Businesses without a real product, UI or substantiated capability.
Start with what visitors need to understand, then decide the page count. A smaller website still deserves thoughtful design.
What gives this design its character?
Choose it only for a real software product with substantial, verifiable capability content; its value is organization, not page count.
- Workflows, integration matrices and a large searchable Skills library create a deeper hierarchy than a brochure site.
- Warm product sections, near-black contrast bands and interface compositions explain how the software works.
- Workflow tabs, full-library search, command copying and case-study videos provide frontend interaction.


Know what sits behind the design.
The original demo declares 176 page routes. 149 Skills entries account for most routes. 176 means neither 176 page designs nor 176 implemented product capabilities.
This maps the original design, not a quoted delivery count. Content examples, language mirrors and utilities are listed separately.
| Page family | Count | Purpose & example |
|---|---|---|
| Home, careers and contact | 3 | Introduce the product, careers and contact optionsView example |
| Product, integrations, Skills and media indexes | 4 | Organize workflows, connected tools, capabilities and media contentView example |
| Product workflow details | 6 | Explain product workflows for interaction analysis, coaching and customer follow-upView example |
| Integration examples | 9 | Describe third-party tools and their integration use casesView example |
| Skills entries | 149 | Explain individual capabilities and tasks, not 149 distinct interface designsView example |
| Media article examples | 3 | Read media articles about the product and its industryView example |
| Legal pages | 2 | Demo legal notices requiring business-specific reviewView example |
- Original demo languages
- English
- Screen layouts
- Responsive desktop and phone layouts
- YUNROU delivery
- A static website connected to your domain
- What can change
- Identity, copy, imagery, page selection and languages
A designed interface is not a connected backend.
AI, MCP, Skills and product panels are explanatory demos, not a working SaaS, connector or AI service. The contact form sends no messages.
Chinese or bilingual pages can be scoped separately. Demo languages do not define your delivery. Pages, translation, media, revisions and maintenance are agreed before work begins.
Does this feel right? Review the scope, then gather your material. The design defines visual and reading character; it does not include every demo page in a quote.
Services & indicative pricesKeep this choice & prepare an enquiry
