Hi, I don't really like to join the discussion, because a) I don't like to tone and b) I don't have time to work on changes or even proposals.
But I'd like to second the general idea by Federico. A website creation less carved in stone and with easier maintainability is something to aim at. Any such suggestions should not be flatly refused. Quite the contrary, changes w.r.t. the website are desperately needed in my opinion and any constructive discussion about that should be allowed and supported. Of course there are many things to consider and of course this has many constraints. But we should not stop here. A separation of manuals and website seems like a sensible thing to me as these are also logically different things (as mentioned: pdf or not, connected with and related to code and versions etc.). And of course the experience of long term ly developers is helpful to tell ideas that won't work from good ones. So please, be friendly and bring together new ideas (innovation) and experience with proven and reliable workflows. It's not easy and quickly done, but imho it's worth the efforts. Cheers, Joram _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel