...

1. Form fields - Magnolia specific fields. 
2. Vaadin fields - Vaadin fields that can be used with Magnolia.
3. Unsupported fields by Maganolia  - Not clear why we specify what Vaadin fields NOT to use. Suggest adding information on what is wrong with each field (i.e. - why it should not be used). That or simply removing this tab.

All three tabs require changes.

Form fields tab

...

After discussions with Andreas and Philip, I would suggest making a few alterations to the Showcase App: Form fields tab:

1. Increase real estate for the fields (i.e make the grey area bigger - stretch it to the left and right).
2. Left align all fields.
3. Add headings:
   
   1. Field name
   2. Appearance
   3. Function (or Description)
4. Consider adding visible columns for headings.
5. Add a short description per field. Say, max 140 characters. (Use this for... Can also be used for... etc.) Where, why, how. (Use on x pages to describe....Try not to use more than x times per page.)
6. Add link to official documentation, where users can find detailed information on using fields. The link could be by the line "Showcase apps......."

...

Vaadin fields and descriptions

1. Increase real estate for the fields (i.e make the grey area bigger - stretch it to the left and right).
2. Group fields thematically or judiciously based on pleasin general aesthetics (does that look neat? If i saw this produced by another company, would I say that this looks nice?)
3. Left align all fields.
4. Add headings:
   
   1. Field name
   2. Appearance
   3. Function (or Description)
5. Consider adding visible columns for headings.
6. Add a short description per field. Say, max 140 characters. (Use this for... Can also be used for... etc.) Where, why, how. (Use on x pages to describe....Try not to use more than x times per page.)
7. Add link to official documentation, where users can find detailed information on using fields. The link could be by the line "Showcase apps......."

...