Why does TaylorUI exist?

The main aims of this UI kit are:

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?

All our projects are unique and styled in very different ways. TaylorUI contains UI elements which you copy into your project and use as a starting point.

What is a "UI Kit"?

TaylorUI is a "UI Kit" and not a "Component Library"... that means there's more than components here. You'll find entire templates for common elements like page sections, navbars, footers. You'll also find reusable hooks and other utilities we've found useful for building UI at Functn.

Data agnostic

As long as your site is built with React and Tailwind, you can use these UI elements with any CMS or datasource you need.

Please give us feedback

If you use a component from the TaylorUI we want to hear from you! Please post any feedback you have in the #taylorui 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 TaylorUI?

Thanks!