Demystifying tables (cells inside; borders outside)
lakesare.brick.do
Demystifying tables (cells inside; borders outside)
1–10 of 23 posts
Re: Demystifying tables (cells inside; borders outside)
#2One point which is missing from this article is how information should be aligned and formatted within cells. This is an underrated feature which can really improve table readability.
For example, right aligned numbers make skimming by size a bit easier.
There's more common UX guidelines but I can't remember them off the top of my head.
Re: Demystifying tables (cells inside; borders outside)
#3One point which is missing from this article is how information should be aligned and formatted within cells. This is an underrated feature which can really improve table readability. For example, right aligned numbers make skimming by size a bit easier. There's more common UX guidelines but I can't remember them off the top of my head.
Sounds interesting, please link me to those guidelines if you stumble upon them!
Re: Demystifying tables (cells inside; borders outside)
#4One point which is missing from this article is how information should be aligned and formatted within cells. This is an underrated feature which can really improve table readability. For example, right aligned numbers make skimming by size a bit easier. There's more common UX guidelines but I can't remember them off the top of my head.
Sounds interesting, please link me to those guidelines if you stumble upon them!
Data Looks Better Naked: Clear Off the Table - https://www.darkhorseanalytics.com/blog/clear-off-the-table
Re: Demystifying tables (cells inside; borders outside)
#5One point which is missing from this article is how information should be aligned and formatted within cells. This is an underrated feature which can really improve table readability. For example, right aligned numbers make skimming by size a bit easier. There's more common UX guidelines but I can't remember them off the top of my head.
Do Share when you have a moment.
Others I have (personal) - Alignment of Headers should match that of content (centre aligned headers = centre aligned content) - Headers should be bolded or another color - Subtotal & grand total should be bolded - Keep same font for both headers & content - Try to keep columns and rows equally sized and spaced - Table heading at the top (IMO) - Avoid using cell (0, 0) that the article talks about
All of the above IMO aids in simplifying the table and hence makes the content stick out more. But granted they are more design principles vs. UX so I too would be keen to learn more about UX guidelines to apply
Re: Demystifying tables (cells inside; borders outside)
#6One point which is missing from this article is how information should be aligned and formatted within cells. This is an underrated feature which can really improve table readability. For example, right aligned numbers make skimming by size a bit easier. There's more common UX guidelines but I can't remember them off the top of my head.
Sounds interesting, please link me to those guidelines if you stumble upon them!
interested too
Re: Demystifying tables (cells inside; borders outside)
#7Earlier quoted context omitted.
Sounds interesting, please link me to those guidelines if you stumble upon them!
Data Looks Better Naked: Clear Off the Table - https://www.darkhorseanalytics.com/blog/clear-off-the-table
Hah, it basically goes into denormalisation!
This certainly looks prettier than the initially shown full-fledged table structure, however I'm having more trouble reading it - it makes me slightly uncertain what text belongs to what row, and whether I properly track the row lines with my eyesight.
Re: Demystifying tables (cells inside; borders outside)
#8One point which is missing from this article is how information should be aligned and formatted within cells. This is an underrated feature which can really improve table readability. For example, right aligned numbers make skimming by size a bit easier. There's more common UX guidelines but I can't remember them off the top of my head.
Sounds interesting, please link me to those guidelines if you stumble upon them!
For anyone interested in building data tables for the web or ERP systems, here are the resources that I have collected (in no particular order):
- https://uxdesign.cc/data-table-for-enterprise-ux-cb48fb9fdf1...
- https://pencilandpaper.io/articles/ux-pattern-analysis-enter...
- https://www.nngroup.com/articles/data-tables/
- https://www.csescienceeditor.org/article/best-practices-in-t... (this one is about print, not web)
- even more guidelines: https://stephaniewalter.design/blog/essential-resources-desi...
Re: Demystifying tables (cells inside; borders outside)
#9That final example with sugar-y (so to speak) grouped headers contradicts prior definition of "normalized table". First "normalized" example explicitly shows that grouping happens exclusively by using text repetition in adjacent headers. Row headers should then read
Treatment, Baseline
Treatment, Contraceptive, 2 weeks
Treatment, Contraceptive, 12 weeks
Treatment, Contraceptive, 20 weeks
Treatment, Recovery phase
Hormones, FSH [IU/L]
Hormones, LH [IU/L]
Hormones, Testosterone [nmol/L]
(From (HTML) accessibility perspective, all tables should better have caption element describing them.)
Re: Demystifying tables (cells inside; borders outside)
#10That final example with sugar-y (so to speak) grouped headers contradicts prior definition of "normalized table". First "normalized" example explicitly shows that grouping happens exclusively by using text repetition in adjacent headers. Row headers should then read Treatment, Baseline Treatment, Contraceptive, 2 weeks Treatment, Contraceptive, 12 weeks Treatment, Contraceptive, 20 weeks Treatment, Recovery phase and…
It does violate the perfect "Cartesian coordinates" normalization I described earlier, however I consider this is a permissible step up over the full normalization, because, while cutting down repetition (entirely), it still suggests a zero-ambiguity way to read off the values from the header cells.