User:NikosA: Difference between revisions
m (→Better typography: fixed ToC will save some long pages!) |
m (First impressions of a custom css designed by archi.tect.gr) |
||
| Line 45: | Line 45: | ||
* indentation of code blocks -- might improve readability | * indentation of code blocks -- might improve readability | ||
* (non-code) text wrapping -- narrower body text column, easier to read | * (non-code) text wrapping -- narrower body text column, easier to read | ||
=== Some proof-of-clean-typography screenshots === | |||
''First impressions of a custom css designed by <http://archi.tect.gr/>'' | |||
The very left column is like a Wiki's connection terminal -- it should look and act like that for the user. It should also clearly state GRASS-GIS' identity. | |||
{| | |||
| [[File:Sample_Navigation_Toolbox_InOther.png|thumb|left|alt=GRASS-Wiki, the main Toolboxes on the left should state GRASS-GIS' robust, clean and open identity|GRASS-Wiki, the main Toolboxes on the left should state GRASS-GIS' robust, clean and open identity]] | |||
|} | |||
Better typography is not only about aesthetics. It's about readability and making things easier to study. The screenshot below speaks for itself. Hint: the ToC is always accessible, following the user's eyes! | |||
[[File:Sample_of_Content_and_ToC_on_the_Right.png|center|border|alt=GRASS-Wiki, better typography, ToC follows scrolling down and therefore always visible|GRASS-Wiki, better typography, ToC follows scrolling down and therefore always visible]] | |||
The Table of Contents is a must have for page-content organisation and navigation. Can it be *always* accessible while not distracting the user from reading when not required? Yes, it can. | |||
{| | |||
| [[File:Sample_Semi_Transparent_ToC.png|frame|left|alt=GRASS-Wiki, semi-transparent ToC, fixed on the right|GRASS-Wiki, semi-transparent ToC, fixed on the right]] | |||
| [[File:Sample_Pointer_over_ToC.png|frame|left|alt=GRASS-Wiki, clean ToC when hovering over with mouse pointer, fixed on the right|GRASS-Wiki, clean ToC when hovering over with mouse pointer, fixed on the right]] | |||
|} | |||
The Categories bar, finally can receive the attention it deserves! | |||
[[File:Sample_Categories_bar.png|frame|center|border|alt=GRASS-Wiki, clean and attractive Categories bar|GRASS-Wiki, clean and attractive Categories bar]] | |||
Related sources: | Related sources: | ||
* http://www.kaikkonendesign.fi/typography/section/1 | * http://www.kaikkonendesign.fi/typography/section/1 | ||
=== Distance between ToC and 1st Section === | === Distance between ToC and 1st Section === | ||
Revision as of 01:12, 16 January 2013
Nikos Alexandris
Other userpages
Contact
nik at nikosalexandris dot net
Scratching ideas for the GRASS-wiki
Various ideas discussed with <http://archi.tect.gr/>
Testing will take place on:
- http://grasswiki.osgeo.org/wiki/User:NikosA/common.css
- http://grasswiki.osgeo.org/wiki/User:NikosA/monobook.css
GRASS-GIS logo
 |
GRASS-Wiki native colors
Should GRASS-Wiki pages wear GRASS' native colors?
Or else... ?
Some random example: light grey font-color (#dcdcdc), green border (#4da948)
Also,
- style the tab-bar to approach the grass-gis website?
Better typography
Review and possibly alter:
- move ToC on the right, make it fixed! This will "save" some long pages!
- linespacing (between hierarchy elements!)
- indentation of code blocks -- might improve readability
- (non-code) text wrapping -- narrower body text column, easier to read
Some proof-of-clean-typography screenshots
First impressions of a custom css designed by <http://archi.tect.gr/>
The very left column is like a Wiki's connection terminal -- it should look and act like that for the user. It should also clearly state GRASS-GIS' identity.
 |
Better typography is not only about aesthetics. It's about readability and making things easier to study. The screenshot below speaks for itself. Hint: the ToC is always accessible, following the user's eyes!
The Table of Contents is a must have for page-content organisation and navigation. Can it be *always* accessible while not distracting the user from reading when not required? Yes, it can.
 |
 |
The Categories bar, finally can receive the attention it deserves!
Related sources:
Distance between ToC and 1st Section
Match Media-Wiki's bigger distance from ToC to 1st Section!
 |
 |
Distance between Sections
Seems to be the same, for some reason, anyhow, some lengthy GRASS-pages look overfilled/noisy!
 |
 |
The GRASS-Wiki Special Pages are nicely structured, easy to read. Is there, and what exactly, a formatting difference with the "dafault" GRASS-Wiki pages?
