A great example of an open source project's website is blender.org. It has an excellent design and it gives you all the information you need to know. The old version of their website can be found on archive.blender.org
On Nov 29, 2016 7:15 AM, "Thiago Censi" <tace...@gmail.com> wrote: > I am new here, but I leave my 2 cents nonetheless. > > I really like the site that John built, and I agree with his approach. If > he asked what the community felt about building a new website, he maybe > wouldn't get to build it. And he is just asking for opinions ;-) > > As for accessibility, I believe it is a very important matter. IMHO there > should not be two different websites. I didn't check John's source, but I > think it would not take a lot of time to make it accessible, if it is coded > properly. As for JS, the best approach would be use progressive > enhancement, adding the scripts and additional functionality if the user's > browser supports it. > > As for WordPress, I am a WP developer myself and understand the concerns. > WP is open source, which is a good thing, but as it is used in more than > 1/4 of the websites, it becames a target to hackers and script kiddies. It > takes time and effort to maintain, upgrade, etc. > > Also, I am not familiar with the multi-lingual plugins so the site can be > translated, the ones I know of I don't really like the approach. > > A static website generator, like Jekill or Pelican, can be a good tool and > maybe more suited to the automatic built already used -- that's > speculation, since I know nothing about the current build tool used :-D. > > Cheers! > > > On Tue, Nov 29, 2016 at 8:47 AM, Urs Liska <u...@openlilylib.org> wrote: > >> >> >> Am 29.11.2016 um 11:25 schrieb Federico Bruni: >> > What John did can be easily done with a static site generator, which >> > would have many more chances to get accepted by LilyPond developers. >> >> One point that hasn't been raised in *this* thread is that using any CMS >> on the donated web space we have is out of question. Anyone wanting to >> have a WordPress site (or anything else) would have to find a hosting >> solution for this - and would probably also be responsible for keeping >> that safe and running. >> >> I personally would also be happy to have the website separate from the >> docs, so it can be adapting to new ideas more easily. But I would much >> more like to see it created by a static site generator, in a system >> where the content can be managed as a Git repository. >> >> This doesn't say *anything* about the visual aspect of the current >> proposal, though. >> >> Urs >> >> _______________________________________________ >> lilypond-user mailing list >> lilypond-user@gnu.org >> https://lists.gnu.org/mailman/listinfo/lilypond-user >> > > > > -- > tacensi. > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
