Skip to content
Permalink
Browse files

docs: link to the original blog post instead of medium (#1844)

  • Loading branch information
lukasbuenger authored and tannerlinsley committed Jan 10, 2020
1 parent 5486293 commit 5f9950339b9cffdd8c66a8c043ef21bb2233a276
Showing with 1 addition and 1 deletion.
  1. +1 −1 docs/concepts.md
@@ -2,7 +2,7 @@

## React Table is a "headless" UI library

React Table is a headless utility, which means out of the box, it doesn't render or supply any actual UI elements. You are in charge of utilizing the state and callbacks of the hooks provided by this library to render your own table markup. [Read this article to understand why React Table is built this way](https://medium.com/merrickchristensen/headless-user-interface-components-565b0c0f2e18). If you don't want to, then here's a quick rundown anyway:
React Table is a headless utility, which means out of the box, it doesn't render or supply any actual UI elements. You are in charge of utilizing the state and callbacks of the hooks provided by this library to render your own table markup. [Read this article to understand why React Table is built this way](https://www.merrickchristensen.com/articles/headless-user-interface-components/). If you don't want to, then here's a quick rundown anyway:

- Separation of Concerns - Not that superficial kind you read about all the time. The real kind. React Table as a library honestly has no business being in charge of your UI. The look, feel, and overall experience of your table is what makes your app or product great. The less React Table gets in the way of that, the better!
- Maintenance - By removing the massive (and seemingly endless) API surface area required to support every UI use-case, React Table can remain small, easy-to-use and simple to update/maintain.

0 comments on commit 5f99503

Please sign in to comment.
You can’t perform that action at this time.