Describe the solution you'd like
run a github workflow that runs on mac, windows, and linux and they all build their system relative apps (Make them parallel so things are faster)

include that in the release-it script

Add release-it as a versioning tool amongst the packages.
each package will have it's own separate version

• ui
• styles
• common
• web
• mobile
• desktop

Find a way to prefix classNames with giffy_css- in build to avoid conflicts with global classes as seen with storybook

• prefix the classes with giffy_css- in build

https://vitorgouveia.github.io/Giffy

Is your feature request related to a problem? Please describe.
When subscribe to newsletter button is clicked no feedback is given to the user

Describe the solution you'd like
make the button green if it worked or put an error on the input it anything went wrong

• Large Logo

• Small Logo

• Link

• Link Hover

• Link Visited

• Tab

• Tab Hover

• Tab Active

• Button

• Input

• Divider

• Modal

Make so button can have a icon attached to them

Describe the bug
The way links are setup with instead of next/link causes error with Github Pages deploy, which requires a 'Giffy' prefix at the start of every link

To Reproduce
Steps to reproduce the behavior:

1. click any link on the blog homepage

Expected behavior
expected links to automatically add the prefix to the link

Possible Solution

• use next as a 'peerDependency' in the ui lib project, that allows us to use the next/link component all over the ui lib
• have the ui lib ask for a React Context with some information that would be shared throughout the components, and in the context ask for a default link prefix or a default link element, then consume that context in the _app

Desktop (please complete the following information):

• OS: Cutefish
• Browser: Brave
• Version: 97

Describe the bug
Blog homepage is inheriting the default description from giffy