Help Center
帮助中心
Aliases:帮助中心帮助页帮助文档客服帮助页常见问题页FAQ 页说明书页面怎么用的页面
What is it
A self-service support page gathering docs, FAQs and contact routes: search guesses intent, articles group by topic, and contact sits at the bottom.
Interactive playground
Try it. Make an informed choice.Loading lab…
✓ When to use
- Users look for answers on their own first
- Support volume needs to be deflected into docs
- Content is maintained by product area over time
✕ When not to use
- Urgent incidents needing live humans — use live chat or a hotline
- Only a few scattered tips — inline hints or tooltips suffice
- Public marketing overview — a landing page fits
Variants
Help Portal
门户型
Search plus category cards, the fullest coverage
FAQ
常见问题
A collapsible Q&A list, lightweight and direct
Docs Hub
文档型
Sidebar outline plus article, for long documentation
Page structure
- 01
Search hero
One line of orientation plus a large search box with title suggestions while typing.
- 02
Topic grid
Entry cards grouped by product area, with icons and article counts.
- 03
Article list
Articles ranked by popularity and recency within a topic.
- 04
Popular
Quick links to frequent questions that shortcut the search.
- 05
Contact support
The fallback route to live chat or a ticket.
- 06
Footer
Service status, community and legal links closing the page.
Implementation
gridflexgrid-template-columns: repeat(auto-fit, minmax(220px, 1fr))position: stickyPin the search hero and filter article titles as the user types (250ms debounce); lay topics out as an auto-fit card grid that collapses to one column on narrow screens. Pair the article list with a popular rail, and close with a full-width contact block. A no-results search shows popular terms and the contact route instead of a blank.
Related concepts
A vertical list of collapsible sections: clicking a header expands its content and clicking again collapses it, either exclusively (one open at a time) or independently. Packs grouped content into limited space for on-demand expansion.
ComponentsContainsA self-contained rectangular container outlined by rounded borders or a surface colour, aggregating related content: cover, title, excerpt and actions. The universal display unit of content feeds, dashboards and commerce lists.
ComponentsContainsNarrows a large list to whatever matches the current input: every keystroke filters the list in place, with hit counts and an empty-state hint. Finding becomes pruning — no submit, no page jump, feedback stays right in front of the user.
PatternsUses patternLayer the information: show only the most common and necessary parts first, hiding secondary details behind "expand", "next step" or "show more" until the user asks for them. It solves the problem of overwhelming users at once — the initial cognitive load stays low and the surface easy to learn, while depth remains available on demand for advanced users.
PatternsUses patternWhen a list or page has no data, don't leave a void — fill it with an illustration, one sentence of explanation and a clear next action. It solves the "blank screen" problem where users can't tell what happened or what to do next, turning dead space into a starting point: onboarding for first use, a way out for fruitless searches.
PatternsUses pattern