rubinhozzz/UXguidelines.txt

## UXguidelines.txt
Forms
-----
- Double points at the end of labels.
- By preference use form horizontal.
- Use (*) and bold style for mandatory fields.
- "Save" button must have primary color and be on the very right side.
- "Close" button must have secondary color and be left side of "Save".
- "Delete" button must have danger color and be left side of the whole window.

Tables
------
- All text left aligned
- All numbers right aligned
- Single characters are centered
- Numbers that are not values, like product codes for example, are treated like text and left aligned.
- Use the same number of decimal places for all numbers in a column
- Left align dates.
- Use 2 digits and leading zero for day numbers (this may be cultural?), and use the same format for dates throughout
- Headers, generally, should carry whatever alignment their data has. This keeps the vertical lines of the table clean, and provides consistency and context.
	Forms
	-----
	- Double points at the end of labels.
	- By preference use form horizontal.
	- Use (*) and bold style for mandatory fields.
	- "Save" button must have primary color and be on the very right side.
	- "Close" button must have secondary color and be left side of "Save".
	- "Delete" button must have danger color and be left side of the whole window.

	Tables
	------
	- All text left aligned
	- All numbers right aligned
	- Single characters are centered
	- Numbers that are not values, like product codes for example, are treated like text and left aligned.
	- Use the same number of decimal places for all numbers in a column
	- Left align dates.
	- Use 2 digits and leading zero for day numbers (this may be cultural?), and use the same format for dates throughout
	- Headers, generally, should carry whatever alignment their data has. This keeps the vertical lines of the table clean, and provides consistency and context.