Foundation based
Spacing, width, and type use shared website tokens.
Studio를 준비하고 있습니다…
Studio를 준비하고 있습니다…
NEXDATAFORGE / VISUAL FOUNDATION
Design Language: reference document →
Website section patterns compose Stage 2 foundation tokens and Stage 3 primitives. They are data-driven, theme-independent, and avoid page-specific hard-coded content.
Short desktop copy receives enough width first, then wraps naturally on tablet, mobile, and 320px screens.
Feature cards are markup inside the section, not a premature MarketingCard component.
Spacing, width, and type use shared website tokens.
Desktop columns collapse to a mobile single-column flow.
Semantic tokens allow later theme layers to restyle the section.
The service card shape remains section-owned until repeated needs prove a component gap.
Turn requirements into clear section plans.
Build reusable sections from shared primitives.
Keep production, reference, and planned states separate.
Metrics can support credibility and social proof without a separate social proof component.
Stage 4 stops at section patterns. Stage 5 should arrange them into page templates.
Core Accordion remains deferred until repeated disclosure needs are proven.
This pattern provides composition only. It does not connect to a backend submit flow.
No separate logo primitive is needed at this stage.
Quote/person/role/avatar are pattern data, not separate production components yet.
The system made each page decision easier to review.
The pattern layer keeps marketing work consistent.
We can now discuss templates without rebuilding basics.
--ndf-website-container--ndf-website-section-space--ndf-website-heading-width의미와 상태를 분명히 하고, 실제 행동과 연결합니다.
장식만을 위해 강조하거나 색·크기만으로 상태를 전달하지 않습니다.
Keyboard focus, 충분한 대비, semantic HTML, 명확한 label, 44px 터치 영역과 320px 화면을 확인합니다.