Which approach supports building reusable components across pages?

• A. Create isolated one-off components.
• B. Build a shared component library with clear usage guidelines.
• C. Avoid documenting usage.
• D. Hard-code styles in every page.

Answer: (B)

Creating reusable components across pages works best when you establish a shared component library with clear usage guidelines. A centralized library standardizes elements like buttons, inputs, cards, and modals, giving a single source of truth that can be versioned, tested, and reused everywhere. Clear guidelines spell out how each component should be used, including props, default values, allowed styles, accessibility considerations, and responsive behavior, so developers know how to integrate them consistently. This approach reduces duplication, prevents visual drift, and speeds up development because updates to a component apply everywhere it's used. In contrast, making isolated one-off components leads to fragmentation, without documentation it’s hard to reuse components correctly, and hard-coding styles on individual pages ties components to specific pages, hindering reuse.