react-table VS chakra-ui

5. react-table

import ReactTable from 'react-table'...render() { return ( )} However, on their API Docs and examples, they all use useTable.

I have a functional component built around the React Table component that uses the Apollo GraphQL client for server-side pagination and searching. I am trying to implement debouncing for the searching so that only one query is executed against the server once the user stops typing with that value. I have tried the lodash debounce and awesome debounce promise solutions but still a query gets executed against the server for every character typed in the search field.

Official Website: https://chakra-ui.com/

Discover Chakra UI: Chakra UI Documentation

This error related to the ReactMarkdown component and the useDisclosure hook in the @chakra-ui/react.

We settled on Chakra (https://chakra-ui.com/). Although we also abandoned our ambitions of a Next.js migration, so... I guess it didn't really end up mattering all that much anyway.

4.chakra-ui

🔍 Site ⭐ GitHub

Examples: radix-ui, chakra-ui, shadcn/ui, tailwind-ui.

(I'm a frontend dev, but I came into the design side only later in my career, after having started as a full-stack programmer.)

I think this book is probably the single best resource I've seen on the topic: https://www.refactoringui.com/

It's a really easy-to-use format (one quick tip on each page, with clear examples).

It's from the people who made Tailwind, a CSS framework that's basically a reimagining of Bootcamp for the Javascript/component era.

Check out some of their templates: https://tailwindui.com/templates

These are lookalike "modern" designs that you can pay to use, or just draw inspiration from. Imitation == flattery and all that.

Along similar lines, check out the free Next.js templates: https://vercel.com/templates/next.js

If you want to build up from components instead, Tailwind offers a component library too: https://tailwindui.com/components

For React, I prefer the astoundingly good MUI framework (amazing components with lots of customizability, a good enough default look, and great documentation): https://mui.com/ If you end up going this route, using their Figma kit (https://mui.com/store/items/figma-react/) plus the Refactoring UI book from above should allow you to whip up a pretty standard-looking, "pretty enough" design in very little time. And then implementing it using the actual MUI lib would just take a few days.

There's also Ant Design: https://ant.design/

And Chakra UI: https://chakra-ui.com/

-----------

For more theoretical stuff (i.e., less visual but still very valuable), the UX research group Nielsen Norman still has a treasure trove of valuable advice: https://www.nngroup.com/articles/top-ten-guidelines-for-home...

You should know the basics of accessibility (beyond general usability, this alos means alt text, header levels, contrast ratios, readability, screen readers, keyboard navigation, special considerations for the hard of sight and hearing, etc.): https://www.w3.org/WAI/standards-guidelines/wcag/ or at least use an easy checklist tool like Microsoft's WCAG analyzer: https://accessibilityinsights.io/