BRC documentation improvement

[marcopiii]

I'm finding several issues in the documentation of BRC. I'm going to list all the ones I find here.

1. Part of the documentazione is scritta in italian and parte in english 🤨

2. The documentation of every component starts with a copypaste-able example of its import, but the path of the module is never wrapped between single quotes, so it actually doesn't work and the user has always to fix it. Also, putting it in a darker background would make it more recognizable as a code snippet.

3. Right after the import example, most of components have a props & methods button that opens a table with all the details about its properties and methods. Unfortunately it has no layout around it and a font that makes it very hard to recognize it as a clickable element.

4. The Design Guidelines tab of lots of components just contains a replica of the props & methods grid.

5. A favicon may increase the coolness of BRC suite by 42% (this may not be based on actual data).

Button

6. The Button documentation has as very first example StatefulButton, which actually needs an import that is different from the described one (import { StatefulButton } from 'buildo-react-components/lib/Button';) and in the usage example uses an undocumented property baseState.

7. In the Button size paragraph the small and medium buttons look equals.

8. The Type of buttons paragraph the icon button example has no icon.

Form

9. All the images in the Design Guidelines tab are missing (broken URL)

LoadingSpinner

10. The guidelines say that "the dimmed layer should cover only the loading section" but by default it covers the whole screen. I think the documentation should provide some information to handle this.

Textarea Autosize

11. In the examples, all the textareas can be stretched way over theirs containers. This should not happen, and the guidelines may refer to this problem and how to avoid it.

12. The Styled components snippet gives error

Dropdown

13. The panel with documentation about props & methods is completely missing

[ggallace]

Come logica, suggerirei di fixare le parti che non richiedono analisi di usabilità o tempo eccessivo per risolvere.

Distinguerei anche improvements/bugs e design/contenuto

@alessandravilla e @giogonzo valutate voi quale portare avanti

[giogonzo]

Come discusso offline con @Aslug , I believe some of the points above can be solved with low effort (0 effort di design). @Aslug could you try to list a few of the soluzioni possibili per i punti that seem easily actionable to you?