AutoHotkey Community

I prefer Sidola examples (my opinion, but did you played with line-height too?), and yes Lexikos it is contradictory : high font-size make a word or a line more readable but make the page less readable, same for high line-height who make lines readable but break paragraph or other block...

However I like your example about MSDN desktop (0.875em font), it is perfect for an half screen with small content, if you want to include a tree then why not, but inside AHK docs some page have a lot of remarque and that will use too much my wheel, too far, so not very designed for a long content (or give up during search).

Other web standards http://www.google.com/ http://www.bing.com/ http://www.facebook.com/..., font and space optimized for a quick search and for habits (not for memory)... I guess that 0.8em is the best, but I can't check on mobil or big screen, but I know a lot of guy who play with body size or ctrl+wheel (big screen, blind, old...)
But it still an opinion based an my old 19" screen, an I opened some real books and checked the font size. Printing rules, do the test ! (discard child book and huge airport novel)

That reminded me a thread about Microsoft Word and Time New Roman at size 11 or 12, lol

Is it just me or has someone reverted the online documentation?

Zelio wrote:high font-size make a word or a line more readable but make the page less readable,

I disagree. Smaller font can make searching quicker - assuming you can read the smaller font and assuming you can't just use the browser's/help viewer's built-in search.

same for high line-height who make lines readable but break paragraph or other block...

Are you inferring that the current line height is too much? I don't think it is.

that will use too much my wheel, too far

There are more efficient ways to scroll long distance.

Don't like big text? Zoom out. Or change the font settings in your browser. Personally, I think there are too many websites which ignore those settings.

Sidola wrote:- Added a gray background to each minor-header,

Why backgrounds on some headers and lines on others? Why grey? Personally, I think black on grey background is less readable. I also think the font size you have chosen is less readable. (But if text that size didn't give me eye strain after a while, I would say it's no more or less readable.)


MSDN does not use underline or backgrounds on headers, nor does it use tables for parameters in most cases. I've been using MSDN for longer than I've known about AutoHotkey, and have always found it to be effective and (for the most part) readable. My only complaint is that sometimes the font is too small.

lexikos wrote:Is it just me or has someone reverted the online documentation?

It certainly has changed. This is what I'm seeing now:
http://imgur.com/wrjuWF8

(which I like 100x better)

(which I like 100x better)

And yet, the parameters still aren't in tables...

lol ya but the whole page is much easier to read

I would still prefer the tables, as I think they are more readable too. But I can live without

You still don't make sense to me. My conclusion from this is that you are strange.

I have incorporated some of the suggestions from this thread. If that's not enough, tough cookies.

lol so be it. i guess all 5 responders in this thread are all strange simultaneously

I was browsing some commands and didnt like the new format at all. Had to go to autohotkey.com, where the old format feels like a good friend who have taught me my first language. So many hours has been spent studying these pages and thanks to its incredible pedagogical layout, ahk is actually easy to learn. The old format is the best and well liked by so many, please dont change it!

Tough weird delicious cookies.

I liked the new style, despite my nostalgia for the old docs.
I think using the same colors as the new homepage was a nice touch.

as if the new homepage is a design spectacle

The http://ahkscript.org/docs/Tutorial.htm page has a "home" link on the top right menu - but other doc pages don't for example http://ahkscript.org/docs/commands/WinGetText.htm

If you find a doc page via a search engine you won't be able to go to the homepage - so perhaps adding a "home" link to all pages might be a good idea.

Ragnars docs in German has nice a nice navigate option on the side... What if we were to put an iframe for navigation on the side?

See #95 Navigation components.

Thanks fincs, yes i remember talking about this in the German forum with Ragnar.

fincs wrote:See #95 Navigation components.

very nice.

and the <hr>s under the green headings make the doc pages much more readable (edit: actually looks like its a border-bottom but w/e)

compare
http://ahkscript.org/docs/commands/WinGetText.htm
and
https://googledrive.com/host/0Bw_Sh-zoq ... etText.htm

+1

+1

+1 to Navigation component!

guest3456 wrote:

fincs wrote:See #95 Navigation components.

very nice.

and the <hr>s under the green headings make the doc pages much more readable (edit: actually looks like its a border-bottom but w/e)

compare
http://ahkscript.org/docs/commands/WinGetText.htm
and
https://googledrive.com/host/0Bw_Sh-zoq ... etText.htm

Oh wow, that is so much more easier to navigate. The header is separated from the rest, and the wide (long? I mean along the x axis) horizontal lines make clear visual distinctions between sections.