Junio C Hamano <gitster@xxxxxxxxx> wrote: > True. Unless we are going to revamp the text in some major way so > that we produce "true" HTML, not just the text source enclosed in a > <pre></pre> pair, I would think we are better off keeping it not > passed to AsciiDoc and leaving it in text format. After all, modern > browsers, which I presume those who want HTML output files would > read them with, can display plain text files just fine, don't they? I am not sure whether that's a good idea or not. As I come from web dev background, I know that people get bored if they need to read a plain-text long article. SEO optimisation also need some beautiful designing of articles so that people can spend more time with visual ease. Of course, git doesn't need any SEO optimisation as it is very much popular. But readers want some visual satisfaction while reading Docs. That's why some people complain about GNU sites (git's site is beautiful by the way). Obviously, here I am using `people` to refer non git developers who are curious about git internals. Thanks :)
