You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 26, 2020. It is now read-only.
The page formatting should be unified and visually clarified.
Most of the texts are spread edge to edge without any margins but some paragraphs are placed in tables. Then the width of a table cell is sometimes limited and sometimes not. Look at the Rendering-section for example.
The pages are also real "old-skåål" in the sense, that they have been written before .css-technique.
Navigating between sections could be improved, so you don't always have to back with the browser to get to the table of contents to find your next point of interest.
There may be a few challenges in getting it right as sometimes the visualization needs to take it's own space. However I'd suggest to:
Use proper margins (100 px ?)
Limit the content width readable
Use .css(es)
Add navigation bars
Review the used fonts. For reference, GitHub is using the best on-screen fonts I have seen so far.
At first I'd probably suggest .css:es. On the longer run we might consider php to collect the content of each page. That part is quite logical and effortless to use but php also offers a lot of toys, that probably would not be useful in this case (fancy ways of animating page changes etc).
Low level browser adaptation should be good enough and no device dependent adaptation. I think it is safe to assume tabletop or laptop usage and not so much pocket size devices. (Though, setting it up to recognize the platform is not that difficult but then we'd go JavaScript. Androids mostly respond in a predictable manner, but the late Windows phones were an ultimate disaster in interpreting the mark-up code.)
The page formatting should be unified and visually clarified.
There may be a few challenges in getting it right as sometimes the visualization needs to take it's own space. However I'd suggest to:
At first I'd probably suggest .css:es. On the longer run we might consider php to collect the content of each page. That part is quite logical and effortless to use but php also offers a lot of toys, that probably would not be useful in this case (fancy ways of animating page changes etc).
Low level browser adaptation should be good enough and no device dependent adaptation. I think it is safe to assume tabletop or laptop usage and not so much pocket size devices. (Though, setting it up to recognize the platform is not that difficult but then we'd go JavaScript. Androids mostly respond in a predictable manner, but the late Windows phones were an ultimate disaster in interpreting the mark-up code.)