Re: Potential improvements to the homepage?

Il giorno mer 16 nov 2016 alle 21:07, Flaming Hakama by Elaine ha scritto: Some comments in response to the most recent (but not quite actually recent) iteration of the perennial web site discussion. State of Translation Looking at the translated versions of

Re: Potential improvements to the homepage?

Some comments in response to the most recent (but not quite actually recent) iteration of the perennial web site discussion. State of Translation Looking at the translated versions of the website, most of the content from the homepage isn't actually translated, but remains in English. Even

Re: Potential improvements to the homepage?

David Pirotte writes: > Hello David, > >> > I was talking about the source code of these web sites, > >> The "source code of these web sites" is also written in Texinfo. > > Nope, Guile, Guix and the other examples I gave all have their > web-site source code > written in

Re: Potential improvements to the homepage?

Hello David, > > I was talking about the source code of these web sites, > The "source code of these web sites" is also written in Texinfo. Nope, Guile, Guix and the other examples I gave all have their web-site source code written in scheme. > That's because Guile does not have its web

Re: Potential improvements to the homepage?

David Pirotte writes: > Hello Urs, > >> So that explains something. >> You think LilyPond's website and docs are maintained as HTML files? >> Not at all! > > Nope, I never said the doc was written and maintained in 'html' :). You can > follow > the doc link on Guile's web-site,

Re: Potential improvements to the homepage?

Hello Urs, > ... > >> Still needs to be tied into the translation process and means another > >> technology the translators need to master. > > > >Translators would edit the strings , then run 'make www' > > ... > So that explains something. > You think LilyPond's website and docs are

Re: Potential improvements to the homepage?

Am 27. August 2016 23:26:31 MESZ, schrieb David Pirotte : > >> > Don't be! You'll get use to it a lot faster then you think! It >> > actually reads almost as if it was English [and *nod* a lot easier >> > then the corresponding html page], here is a simplified example. >The >> >

Re: Potential improvements to the homepage?

> > Don't be! You'll get use to it a lot faster then you think! It > > actually reads almost as if it was English [and *nod* a lot easier > > then the corresponding html page], here is a simplified example. The > > schema is the same for all pages: > > > > import > > utils > > shared >

Re: Potential improvements to the homepage?

David Pirotte writes: > Don't be! You'll get use to it a lot faster then you think! It > actually reads almost as if it was English [and *nod* a lot easier > then the corresponding html page], here is a simplified example. The > schema is the same for all pages: > > import >

Re: Potential improvements to the homepage?

> > ... or rather strings in a scheme file? Here's a scary example: > > http://git.savannah.gnu.org/cgit/guix/guix-artwork.git/tree/website/www/about.scm > > > This approach, at least this example, is totally missing CSS/JavaScript > integration that makes (and, unfortunately, often breaks)

Re: Potential improvements to the homepage?

On Wed, 24 Aug 2016 17:13:50 +0200 Federico Bruni wrote: > ... or rather strings in a scheme file? Here's a scary example: > http://git.savannah.gnu.org/cgit/guix/guix-artwork.git/tree/website/www/about.scm This approach, at least this example, is totally missing

Re: Potential improvements to the homepage?

Hi Federico, > Il giorno mer 24 ago 2016 alle 0:00, David Pirotte ha > scritto: > > The first thing, imo, would be to have these pages rewritten in > > scheme, Guile scheme > > I mean of course :), with the portion of the code that holds the > > content being > > expressed

Re: Potential improvements to the homepage?

Il giorno mer 24 ago 2016 alle 19:13, Noeck ha scritto: Last year we had this discussion: https://lists.gnu.org/archive/html/lilypond-devel/2015-07/msg00105.html And in this discussion, sort of agreed that the website (the first page you look at and some few

Re: Potential improvements to the homepage?

Hi, > Last year we had this discussion: > https://lists.gnu.org/archive/html/lilypond-devel/2015-07/msg00105.html And in this discussion, sort of agreed that the website (the first page you look at and some few others) are different from all the docs and so on. Switching the docs in all

Re: Potential improvements to the homepage?

Il giorno mar 23 ago 2016 alle 17:51, Jacques Menu Muzhic ha scritto: Would a CMS like WordPress be a good candidate for a complete rewrite? I don’t know what is needed behind the scenes to satisfy the needs of such a web site. Absolutely not, for a number of reasons.

Re: Potential improvements to the homepage?

Il giorno mer 24 ago 2016 alle 0:00, David Pirotte ha scritto: The first thing, imo, would be to have these pages rewritten in scheme, Guile scheme I mean of course :), with the portion of the code that holds the content being expressed using sxml, see below for examples.

Re: Potential improvements to the homepage?

Hi David, > Two beautiful examples, imo: > GNU Guix > https://www.gnu.org/software/guix/ > GNU Guile > https://www.gnu.org/software/guile/ The second is, IMO, far more attractive than the first. But no doubt there are people on this list who prefer the

Re: Potential improvements to the homepage?

Hi Paul (et al.), > I think the contents of the home page could use some changes as much or more > than style. Maybe as much… but not more than. ;) > I'd say the home page should focus on new visitors. +1 > Simple things could go a long way, like moving the examples >

Re: Potential improvements to the homepage?

On Tue, Aug 23, 2016 at 4:44 PM, Paul wrote: > I think the contents of the home page could use some changes as much or > more than style. Simple things could go a long way, like moving the > examples (http://lilypond.org/examples.html) to the home page. Those > images show

Re: Potential improvements to the homepage?

I think the contents of the home page could use some changes as much or more than style. Simple things could go a long way, like moving the examples (http://lilypond.org/examples.html) to the home page. Those images show LilyPond's (arguably) best aspect, its high quality engraving. They

Re: Potential improvements to the homepage?

Hello, > >>> Would a CMS like WordPress be a good candidate for a complete rewrite? I would not do that. The first thing, imo, would be to have these pages rewritten in scheme, Guile scheme I mean of course :), with the portion of the code that holds the content being expressed using sxml,

Re: Potential improvements to the homepage?

On 8/23/2016 1:14 PM, David Kastrup wrote: > I think Texinfo has some manners of including such content, Good. I'm not familiar with the system, but due to the sort of work I see being done with it here, it's not surprising there would be such a feature. > and I believe the CSS to more or less

Re: Potential improvements to the homepage?

Karlin High writes: > On 8/23/2016 11:20 AM, David Kastrup wrote: >> Jacques Menu Muzhic writes: >>> Hello, >>> >>> Would a CMS like WordPress be a good candidate for a complete rewrite? >> At the current point of time, the Texinfo generated output

Re: Potential improvements to the homepage?

On 8/23/2016 11:20 AM, David Kastrup wrote: > Jacques Menu Muzhic writes: >> Hello, >> >> Would a CMS like WordPress be a good candidate for a complete rewrite? > At the current point of time, the Texinfo generated output includes Info > (without translations or images,

Re: Potential improvements to the homepage?

Hi Karlin, I agree with everything you posted and/or linked. However, I think you (and perhaps some others) may be confusing or conflating “modern and inviting” (and its ilk) with “overdesigned” (and its ilk) — they are most definitely not the same thing. > the non-overdesigned Basecamp

Re: Potential improvements to the homepage?

Jacques Menu Muzhic writes: > Hello, > > Would a CMS like WordPress be a good candidate for a complete rewrite? At the current point of time, the Texinfo generated output includes Info (without translations or images, still good for proofreading the primary pages), PDF

Re: Potential improvements to the homepage?

On 8/21/2016 4:19 AM, Andrew Yoon wrote: Nothing dramatic or web3.0 style of course. I have a pet peeve about websites that are so slick and responsive that it becomes a real challenge to find anything on them. The site for a certain popular-in-USA accounting software company comes to mind.

Re: Potential improvements to the homepage?

On Tue, Aug 23, 2016 at 05:51:26PM +0200, Jacques Menu Muzhic wrote: > Hello, > > Would a CMS like WordPress be a good candidate for a complete rewrite? I > don’t know what is needed behind the scenes to satisfy the needs of such a > web site. No. Paul > JM > > > Le 23 août 2016 à 16:18,

Re: Potential improvements to the homepage?

Hello, Would a CMS like WordPress be a good candidate for a complete rewrite? I don’t know what is needed behind the scenes to satisfy the needs of such a web site. JM > Le 23 août 2016 à 16:18, Federico Bruni a écrit : > > Il giorno dom 21 ago 2016 alle 11:19, Andrew

Re: Potential improvements to the homepage?

Il giorno dom 21 ago 2016 alle 11:19, Andrew Yoon ha scritto: I'm wondering if there might be room to discuss some improvements to the lilypond.org homepage -- in my personal experience in the past its typical GNU-style dated appearance was a little off-putting, and I

Re: Potential improvements to the homepage?

On Mon 22 Aug 2016 at 08:38:38 (+0200), David Kastrup wrote: > Andrew Yoon writes: > > > There are certainly many options to explore, many of them quite simple. At > > any rate, over the next few days I'll take a crack at something and see > > what people think. Should

Re: Potential improvements to the homepage?

Andrew Yoon writes: > There are certainly many options to explore, many of them quite simple. At > any rate, over the next few days I'll take a crack at something and see > what people think. Should future discussions about this belong in the dev > mailing list? Apologies

Re: Potential improvements to the homepage?

There are certainly many options to explore, many of them quite simple. At any rate, over the next few days I'll take a crack at something and see what people think. Should future discussions about this belong in the dev mailing list? Apologies if this is the wrong place... On Mon, Aug 22, 2016

Re: Potential improvements to the homepage?

On Sunday, August 21, 2016, Urs Liska wrote: > > > Am 21. August 2016 20:58:57 MESZ, schrieb Abraham Lee < > tisimst.lilyp...@gmail.com >: > >On Sunday, August 21, 2016, Andrew Yoon > wrote: > > > >> My thoughts exactly.

Re: Potential improvements to the homepage?

Am 21. August 2016 20:58:57 MESZ, schrieb Abraham Lee : >On Sunday, August 21, 2016, Andrew Yoon wrote: > >> My thoughts exactly. I don't think any drastic change would be called >for, >> I suspect virtually everything that would be productive

Re: Potential improvements to the homepage?

On Sunday, August 21, 2016, Andrew Yoon wrote: > My thoughts exactly. I don't think any drastic change would be called for, > I suspect virtually everything that would be productive could be handled > purely in CSS. Maybe something more in line with the design of >

Re: Potential improvements to the homepage?

Werner LEMBERG writes: >>> Because the Web site looks like it has been left to decay since the >>> time when that design style was current, viewers are inclined to >>> think the software may be in a similar condition. >> >> +1 >> >> That’s definitely one reason — maybe the main

Re: Potential improvements to the homepage?

msk...@ansuz.sooke.bc.ca writes: > On Sun, 21 Aug 2016, David Kastrup wrote: >> Uh, how does "dated appearance" (acl of animated content and flashiness, >> color schemes of last season?) equate to "not very reassuring welcome"? > > Because the Web site looks like it has been left to decay since

Re: Potential improvements to the homepage?

>> Because the Web site looks like it has been left to decay since the >> time when that design style was current, viewers are inclined to >> think the software may be in a similar condition. > > +1 > > That’s definitely one reason — maybe the main one — but there are > many others, of course. >

Re: Potential improvements to the homepage?

Hi all, >> Uh, how does "dated appearance" (acl of animated content and flashiness, >> color schemes of last season?) equate to "not very reassuring welcome"? > > Because the Web site looks like it has been left to decay since the time > when that design style was current, viewers are inclined

Re: Potential improvements to the homepage?

My thoughts exactly. I don't think any drastic change would be called for, I suspect virtually everything that would be productive could be handled purely in CSS. Maybe something more in line with the design of http://lilypondblog.org/ ? But then again, I'm no designer. On Sun, Aug 21, 2016 at

Re: Potential improvements to the homepage?

On Sun, 21 Aug 2016, David Kastrup wrote: > Uh, how does "dated appearance" (acl of animated content and flashiness, > color schemes of last season?) equate to "not very reassuring welcome"? Because the Web site looks like it has been left to decay since the time when that design style was

Re: Potential improvements to the homepage?

Andrew Yoon writes: > Hi everyone - long-time lilyponder, first time poster here - > > I'm wondering if there might be room to discuss some improvements to > the lilypond.org homepage -- in my personal experience in the past its > typical GNU-style dated appearance was a

Re: Potential improvements to the homepage?

Am 21.08.2016 um 15:41 schrieb Andrew Bernard: Hello Andrew and welcome (from another Haskell user!). I agree with you. The website is looking tired and faded. But I think it is somehow generated programmatically from the lilypond builds, and not based on a content management system. I suspect

Re: Potential improvements to the homepage?

Hello Andrew and welcome (from another Haskell user!). I agree with you. The website is looking tired and faded. But I think it is somehow generated programmatically from the lilypond builds, and not based on a content management system. I suspect this makes it difficult to give it a fresh new

Potential improvements to the homepage?

Hi everyone - long-time lilyponder, first time poster here - I'm wondering if there might be room to discuss some improvements to the lilypond.org homepage -- in my personal experience in the past its typical GNU-style dated appearance was a little off-putting, and I suspect for many other