John Roper <johnroper...@gmail.com> writes: > I changed the header size to be smaller. As for the overall design, again, > the front page of the website is supposed to make the user want to take a > look at it. A design such as this does that while a page full of serif text > and two images does not. > > As for the separation of templates and content, that is the way any other > site generator works. Also, there has to be HTML in any generator because > no markup language like markup could do any kind of advanced layout like > that. > > No one expects the website to look like the output of a LilyPond > document. LilyPond does not make websites. Users expect the website > to show them (in a nice-looking way) what LilyPond can do from > examples. There is so much text. The standard human does not want to > read that much text.
Which makes the standard human unsuitable for working with LilyPond where reading documentation cannot sensibly be avoided because there is no GUI constraining/directing your input. That does not mean that the typical prospective LilyPond user just loves wading through walls of text. But it does mean that there is only partial overlap with the objectives of a website trying to sell shoes, and that the best balance for ending up with new users might lead to different weights in the attention-interest-desire-action chain to avoid scoring higher in early stages of the process but with an audience less likely to stay around until the end. It's also worth noting that only part of a website's job is to garner initial interest (and it requires referals to be found in the first place). Another is as a portal for people who already know what LilyPond is and want to get work done. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
