components cleanup

[mbarrenechea]

• [x] Removed most components
• [x] Removed storybook
• [x] Added MDX documentation of the remaining components (map, legend, icon)
• [x] Removed layer-manager and use a custom simple layer-manager on the map implementation instead
• [x] add instructions noting shadcn components should be used whenever possible.
• [x] Install Shadcn and use Button component
• [x] update docs deployment in Vercel from Storybook's to serve '/docs'
• [x] use use-hooks-ts instead of use-debounce package: Is typescript friendly, treeshakeable, with a good amount of stars and good documentation and offers a variety of hooks more than just the use-debounce
• [x] Fix all typing warnings

NEXT:

• Move to Next 13
• Remove Carousel?
• Merge with the map scaffold

NEXT ISSUES:

• Legend: Make accessible by keyboard. DnD kit has an open issue about it: https://github.com/clauderic/dnd-kit/issues/985
• Icons. Should we use a library? To remove webpack. In conversations with the design team

Closes https://github.com/Vizzuality/front-end-scaffold/issues/123

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
front-end-scaffold-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 18, 2023 1:43pm

[Bluesmile82]

I'm updating the PR to recover carousel, cookies, loading and search as they don't exist on shadcn

[andresgnlez]

(This is in the Search component) Not the first time we face this issue and it is basically because react-aria does not support SSR by default and you need their provider. I tried to install it but everything crashed 😅 , so not sure what approach should we follow here... For this kind of things personally I don't like react-aria ecosystem, but I am not sure we are going to be able to find an alternative to @react-aria/searchfield and @react-stately/searchfield..

---

On a different page, when I type in the search component, looks like we are passing invalid properties to the button element, can you take a look at this, please?

[Bluesmile82]

(This is in the Search component) Not the first time we face this issue and it is basically because react-aria does not support SSR by default and you need their provider. I tried to install it but everything crashed 😅 , so not sure what approach should we follow here... For this kind of things personally I don't like react-aria ecosystem, but I am not sure we are going to be able to find an alternative to @react-aria/searchfield and @react-stately/searchfield..

On a different page, when I type in the search component, looks like we are passing invalid properties to the button element, can you take a look at this, please?

I'm using a simple accessible solution now for this component instead react-aria. Please take a look