LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

Mobile Adaptation and Component Assembly Rules for a B2B Component Library

Section:B2B COMPONENT SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「Mobile Adaptation and Component Assembly Rules for a B2B Component Library」 in B2B COMPONENT SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Sites where the same components must serve both desktop and mobile
  • Overseas markets with a high mobile traffic share (especially South Asia, Southeast Asia, South America)
  • Sites that assemble components freely into different page layouts
  • Delivered template sites that drift structurally as clients adjust them themselves
Template / code snippethtml
<!-- 组件容器:桌面端并排,移动端堆叠 -->
<style>
.cmp-grid { display: grid; gap: 24px; grid-template-columns: 1fr; }
@media (min-width: 900px) {
  .cmp-grid { grid-template-columns: 1.6fr 1fr; }
}

/* 表格在窄屏用容器滚动,不隐藏列 */
.tbl-scroll { overflow-x: auto; -webkit-overflow-scrolling: touch; }
.tbl-scroll > table { min-width: 640px; }

/* 长内容不被截断 */
.pd-specs td, .pd-specs th { word-break: break-word; }
</style>

<div class="cmp-grid">
  <div class="cmp-main"><!-- 组件按顺序拼装 --></div>
  <aside class="cmp-side"><!-- 侧栏:证书、资料、CTA --></aside>
</div>

<div class="tbl-scroll">
  <!-- 表格内容 -->
</div>
Fields and parameters
Field / parameterTypeDescription and values
BreakpointNumber900px advised; adjust to the dominant devices of the target market
Grid column countNumber2 columns on desktop, 1 on mobile
Table minimum widthNumber + pxKeeps columns from being squeezed; the container handles horizontal scrolling
Sidebar contentListSecondary information: certificates, document downloads, CTA
Container spacingNumber + px24px advised
Touch targetNumber + pxButtons and links at least 44×44

SEO and structured-data notes

SEO and structured-data checkpoints
Do not hide table columnsHiding columns on narrow screens equals hiding content from crawlers; scroll inside a container and keep all data
Do not truncate long parameter stringsword-break prevents oversized model numbers or values from breaking the layout
Touch targets at least 44pxA high mis-tap rate on mobile directly loses inquiries
Keep component order consistentDesktop and mobile should present the same structure, so one page does not show different structures on the two ends
Do not create separate mobile contentMobile is not a subset of content; removing parameters leaves buyers unable to judge
Move the sidebar after the main content on mobileMain content first; a CTA at the end of the body is less intrusive than a fixed floating bar

Compliance risk notes

  • Do not show only part of the parameters on mobile followed by "contact us for details"; it costs both crawlability and conversion
  • Fixed floating CTAs must not cover content or cause mis-taps
  • Do not reduce parameter precision because mobile traffic is high
  • Popup components must keep their close button easily reachable on mobile

Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.

Modification example

<!-- Modification example: handling tables on narrow screens -->
<!-- Wrong: hiding columns directly in a media query -->
<style>
@media (max-width: 640px) {
  .pd-table th:nth-child(4),
  .pd-table td:nth-child(4) { display: none; }   <!-- ❌ data is hidden -->
</style>

<!-- Right: horizontal container scrolling, data fully preserved -->
<div class="tbl-scroll" tabindex="0" role="region"
     aria-label="Technical specification table, scrollable horizontally">
  <table class="pd-table">
    <!-- all columns kept -->
  </table>
</div>

<style>
.tbl-scroll { overflow-x: auto; }
.tbl-scroll > table { min-width: 640px; }
</style>

<!-- Add a hint so users know the table scrolls horizontally -->
<p class="tbl-hint">Swipe left and right to see all parameters</p>

<!-- tabindex="0" + role="region" lets keyboard users focus and scroll the table;
     this is also a common deduction in accessibility audits. -->

FAQ

How many breakpoints should a component library have?
One or two. More breakpoints raise the client's adjustment cost. One main breakpoint at 900px covers most scenarios.
Why insist that tables never hide columns?
Because mobile pages are crawled by search engines too. Hidden columns make key parameters invisible on mobile and directly hurt the page's content-completeness assessment.
Should components be freely assemblable?
That is the core value of a component library versus a whole-site template. Assembly requires each component to have clear boundaries and minimal dependencies.
What if the client breaks the layout?
Reserve unified class names and CSS variables inside components so changes are traceable, and provide minimal-dependency notes so clients do not break a whole page while tweaking one component.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.

Note: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.