Skip to main content

Making Components Discoverable

Code reuse is a useful advantage of the modularity provided by components. Discoverability is a key factor for sharing reusable components between developers and websites.

In larger organizations using Gatsby, it becomes more important for different teams to be able to browse components used by other teams, in order to avoid reinventing the wheel. Making components discoverable also helps in creating a component design system that helps keep your UX/UI consistent across websites and applications.

Shared components can be organized and made discoverable in a shared component hub like to search, visualize, interact with and consume. Teams can share and discover components, use them in different projects, suggest updates and stay in sync.

If using additional repositories and libraries to share components, tools like StoryBook and StyleGuidist can help develop and visualize components in isolation, creating a visual documentation portal for shared components.

This is a stub. Help our community expand it.

Please use the Gatsby Style Guide to ensure your pull request gets accepted.

See the issue relating to this stub on GitHub
Edit this page on GitHub