Show HN: UI Playbook – A documented collection of UI components

Re:Show HN: UI Playbook – A documented collection of UI comp... by corytheboyd on Wednesday July 22, 2020 @11:52AM (#23918296)

Was wondering why OP only seems to recommend reach-io as examples, turns out they are a contributor. It’s all open source so like, you’re not doing anything malicious for profit here, but it would come across as disingenuous if you didn’t mention being a contributor to the most prominently linked example system if this is supposed to be system agnostic documentation

[ Parent | on HN ]

Re:Show HN: UI Playbook – A documented collection of UI comp... by raunofreiberg on Wednesday July 22, 2020 @12:15PM (#23918587)

The documentation itself is system agnostic. You don’t need to use Reach UI for the docs to make sense.

I recommend Reach UI because in my experience it has worked out great. Feel free to extend the examples with additional libraries! :-)

[ Parent | on HN ]

Re:Show HN: UI Playbook – A documented collection of UI comp... by parhamn on Wednesday July 22, 2020 @11:58AM (#23918386)

> but it would come across as disingenuous if you didn’t mention being a contributor to the most prominently linked example

No it wouldn’t. That’s a lot of disclaimer burden to put on someone.

[ Parent | on HN ]

Re:Show HN: UI Playbook – A documented collection of UI comp... by corytheboyd on Wednesday July 22, 2020 @12:09PM (#23918507)

> That’s a lot of disclaimer burden

No it is not, a disclaimer is very low effort. Here is an example disclaimer: "Just a heads up, I am a Reach-UI contributor!"

That is in no way a large burden, still gets the message out about both UI Playbook and Reach-UI, and is just the more respectable thing to do here. I really don't think OP did anything WRONG, there is clearly no malice here, it's just an observation I had to better communicate in the future for the people like me who care about these details, I know I am not alone here.

[ Parent | on HN ]