Why does the Functn Component Library exist?

The main aims of this component library are to:

1. Speed - We want to make it faster for you to add common website elements to your project.
2. Accessibility - Reduce Accessibility issues by providing components that already meet our high A11y standards.
3. Consistency - Improve the level of consistency accross all our projects at Functn.

How does it work?

When you hear the term "Component Library" you might think of a library like @mui/material or radix-ui. Our component library does not work like these.

All our projects are styled in very different ways, so we've provided a set of components, page sections and site structure that you can use as a starting point. Copy over the code, hook it up to your data and modify it however you need.

Please give us feedback

If you use a component from the component library we want to hear from you! Please post any feedback you have in the #component-library Slack channel. Things we want to hear:

• Did you use a component successfully?
• How much time did it save you?
• Did anything not work?
• Did you add any cool features of your own?
• Was there anything confusing about the component or its documentation?
• What would you like to see in the component library?

Thanks!