Il 09/dic/2013 09:22 "Janek Warchoł" ha scritto:
>
> 2013/12/9 Carl Peterson :
> > 2013/12/6 David Kastrup :
> > > A complete color _scheme_ might be distracting, but it may make sense
to
> > > have a title or side bar or other obvious always on-screen element
> > > color-coded.
> >
> > Okay, so I
2013/12/9 Carl Peterson :
> 2013/12/6 David Kastrup :
> > A complete color _scheme_ might be distracting, but it may make sense to
> > have a title or side bar or other obvious always on-screen element
> > color-coded.
>
> Okay, so I have a patch set ready to go with this. The only differences are
Carl Peterson writes:
> On Sun, Dec 8, 2013 at 5:55 PM, Carl Peterson wrote:
>>
>> I have something in development for #2 on Federico's list. I've parsed
>> through enough of the texi2html script that I was able to insert CSS
>> classes into the tag that will allow me to color code each manual.
On Fri, Dec 6, 2013 at 3:26 AM, Janek Warchoł wrote:
> 2013/12/6 David Kastrup :
> > Janek Warchoł writes:
> >> A suggestion from my colleague: for a long time he kept confusing LM
> >> and NR, and he said that it would be nice if (for example) they had
> >> different color schemes so that one wi
On Sun, Dec 8, 2013 at 5:55 PM, Carl Peterson wrote:
>
> I have something in development for #2 on Federico's list. I've parsed
> through enough of the texi2html script that I was able to insert CSS
> classes into the tag that will allow me to color code each manual.
>
One thing that is very stra
On Sun, Dec 8, 2013 at 5:34 PM, Urs Liska wrote:
> Am 08.12.2013 23:23, schrieb Federico Bruni:
>
>
> 2013/12/6 Federico Bruni
>
>> These problems should be recorded in our tracker.
>> So far I've seen 2 issues/feature requests:
>>
>> 1. improve SEO
>> 2. associate a different color scheme t
Am 08.12.2013 23:23, schrieb Federico Bruni:
2013/12/6 Federico Bruni mailto:fedel...@gmail.com>>
These problems should be recorded in our tracker.
So far I've seen 2 issues/feature requests:
1. improve SEO
2. associate a different color scheme to each manual
I've added them:
2013/12/6 Federico Bruni
> These problems should be recorded in our tracker.
> So far I've seen 2 issues/feature requests:
>
> 1. improve SEO
> 2. associate a different color scheme to each manual
>
>
I've added them:
https://code.google.com/p/lilypond/issues/detail?id=3714
https://code.google.co
On Sat, Dec 7, 2013 at 3:42 PM, Phil Holmes wrote:
>
>
>> My recommendations would be:
>> 1. Use a consistent URL for the latest stable version of LilyPond
>> documentation. That way web searches and other pages across the web link
>> to the latest version instead of ancient versions of the docume
- Original Message -
From: "David Bolton"
To:
Sent: Saturday, December 07, 2013 7:54 PM
Subject: Re: LilyPond Website Work
On 12/7/2013 6:39 AM, Urs Liska wrote:
As can be seen here (one more time):
Am 07.12.2013 08:45, schrieb Janek Warchoł:
2013/12/7 David Bolton :
On 12/7/2013 9:48 AM, Janek Warchoł wrote:
> 2013/12/7 David Kastrup :
>>> It may also be a good idea to find a way to visually distinguish
>>> between the stable and the development sections of website/manual?
>> Stable: solid color in the color coded area.
>>
>> Development: diagonally striped or
On 12/7/2013 6:39 AM, Urs Liska wrote:
>
> As can be seen here (one more time):
>
> Am 07.12.2013 08:45, schrieb Janek Warchoł:
>> 2013/12/7 David Bolton :
>>
>> ...
>>
>> And by the way, why are you using documentation for versions 2.16 and
>> 2.17 while the file is marked as 2.14? This looks like
2013/12/7 David Kastrup :
>
>> It may also be a good idea to find a way to visually distinguish
>> between the stable and the development sections of website/manual?
>
> Stable: solid color in the color coded area.
>
> Development: diagonally striped or patterned in some other way.
+1
__
Urs Liska writes:
> Am 06.12.2013 09:12, schrieb Janek Warchoł:
>> 2013/12/6 Carl Peterson :
>>> Having worked for two corporations that have fairly extensive (and
>>> stringent) visual identity and branding guidelines (colors, typeface,
>>> formatting, etc.), I've learned that there are ways to
Am 06.12.2013 09:12, schrieb Janek Warchoł:
2013/12/6 Carl Peterson :
Having worked for two corporations that have fairly extensive (and
stringent) visual identity and branding guidelines (colors, typeface,
formatting, etc.), I've learned that there are ways to make an obvious
change between two
Am 06.12.2013 21:26, schrieb Janek Warchoł:
Urs,
2013/12/6 David Kastrup :
Urs Liska writes:
I think although not explicitly stated as a feature request the
discussion surely yields
3. Clarify first steps/new user experience.
I don't think that this is the same topic. The listed requests
Urs,
2013/12/6 David Kastrup :
> Urs Liska writes:
>
>> Am 06.12.2013 14:12, schrieb Federico Bruni:
>>> These problems should be recorded in our tracker.
>>> So far I've seen 2 issues/feature requests:
>>>
>>> 1. improve SEO
>>> 2. associate a different color scheme to each manual
>> I think alt
From: "Ryan McClure"
Sent: Friday, December 06, 2013 6:59 PM
I just did a Google search on a computer that I've never used/logged into
before. My account was fresh, and I did these searches without any
previous
history affecting my results:
"Music notation software"
Lilypond came in at
From: "Ryan McClure"
Sent: Friday, December 06, 2013 6:59 PM
I just did a Google search on a computer that I've never used/logged into
before. My account was fresh, and I did these searches without any
previous
history affecting my results:
"Music notation software"
Lilypond came in at 25
g.com
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/LilyPond-Website-Work-was-A-thought-on-Windows-Experience-tp155110p155236.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Fri, Dec 6, 2013 at 11:08 AM, Phil Holmes wrote:
>
> Well, yes, as CPU load. I remain of the view that this is not a good use
> of time - there are other things that will be of greater value for less
> effort. Remember, you'll not be doing this by editing HTML, but the
> texi2HTML control fil
- Original Message -
From: "Phil Burfitt"
To: "Phil Holmes" ; "Carl Peterson"
; "James Harkins"
Cc: "Mailinglist lilypond-user"
Sent: Friday, December 06, 2013 3:59 PM
Subject: Re: LilyPond Website Work (was: A thought on Window
- Original Message -
From: "Phil Holmes"
Sent: Friday, December 06, 2013 3:35 PM
Our server is provided on a goodwill basis, and so we would not want to use
any scripting that might load it.
Carl Perterson wrote:
CSS gradients can be coded for fewer bytes and one less server reques
"Phil Holmes" writes:
> - Original Message -
> From: Carl Peterson
>
>> I want to eventually eliminate any image file that does not
>> contribute to content.
>> The first victim of this will be the gradient images used for the
>> header and navigation backgrounds.
>> CSS gradients can be
- Original Message -
From: Carl Peterson
I want to eventually eliminate any image file that does not contribute to
content.
The first victim of this will be the gradient images used for the header
and navigation backgrounds.
CSS gradients can be coded for fewer bytes and one less serv
On Fri, Dec 6, 2013 at 9:00 AM, James Harkins wrote:
> A side comment, picking up on a comment in the "Windows experience" thread:
>
> I hope the new site will avoid any hooks to Google analytics or other APIs.
> I'm behind the Great Firewall of China, and I see frequently how Google
> dependenci
Urs Liska writes:
> Am 06.12.2013 14:12, schrieb Federico Bruni:
>> These problems should be recorded in our tracker.
>> So far I've seen 2 issues/feature requests:
>>
>> 1. improve SEO
>> 2. associate a different color scheme to each manual
> I think although not explicitly stated as a feature r
Am 06.12.2013 14:12, schrieb Federico Bruni:
These problems should be recorded in our tracker.
So far I've seen 2 issues/feature requests:
1. improve SEO
2. associate a different color scheme to each manual
I think although not explicitly stated as a feature request the
discussion surely yields
A side comment, picking up on a comment in the "Windows experience" thread:
I hope the new site will avoid any hooks to Google analytics or other APIs.
I'm behind the Great Firewall of China, and I see frequently how Google
dependencies cause page loading times to balloon, while the browser wait
Federico Bruni writes:
> 2013/12/6 Phil Burfitt
>
> Carl, you might also like to keep in mind Lilypond's search rankings while
> you redesign.
> This is really bad, I never checked it.
> 1. improve SEO
I guess I'm glad someone notices and seems to care
http://lists.gnu.org/archive/
2013/12/6 Phil Burfitt
> Carl, you might also like to keep in mind Lilypond's search rankings while
> you redesign. A first page listing would bump up traffic considerable, and
> shouldn't be hard to achieve given that whoever designed lilypond's
> homepage hasn't given any thought to SE ranking
Carl, you might also like to keep in mind Lilypond's search rankings while
you redesign. A first page listing would bump up traffic considerable, and
shouldn't be hard to achieve given that whoever designed lilypond's homepage
hasn't given any thought to SE ranking - there's just no relevant tex
2013/12/6 David Kastrup :
> Janek Warchoł writes:
>> A suggestion from my colleague: for a long time he kept confusing LM
>> and NR, and he said that it would be nice if (for example) they had
>> different color schemes so that one will know where to look at things
>> ("hmm, i remember seeing it i
Janek Warchoł writes:
> 2013/12/6 Carl Peterson :
>> Having worked for two corporations that have fairly extensive (and
>> stringent) visual identity and branding guidelines (colors, typeface,
>> formatting, etc.), I've learned that there are ways to make an obvious
>> change between two things w
2013/12/6 Carl Peterson :
> Having worked for two corporations that have fairly extensive (and
> stringent) visual identity and branding guidelines (colors, typeface,
> formatting, etc.), I've learned that there are ways to make an obvious
> change between two things while still making them look li
On Thu, Dec 5, 2013 at 8:13 PM, Carl Sorensen wrote:
>
> On 12/5/13 9:43 AM, "Carl Peterson" wrote:
>
> >
> >1) Review the CSS of both the website and the documentation. These are
> >simply CSS files that don't need any compiling or reconfiguring. The
> >eyesore for me is the documentation, and
On 12/5/13 9:43 AM, "Carl Peterson" wrote:
>
>1) Review the CSS of both the website and the documentation. These are
>simply CSS files that don't need any compiling or reconfiguring. The
>eyesore for me is the documentation, and it would be nice to start to
>move the two into more of a seamless
Hi,
2013/12/5 Carl Peterson :
> Having dived into the git repo and page source a little, here is what I see
> as the "road map" to improving the look of the LilyPond website, with an eye
> toward getting the most benefit the fastest.
> [...]
I have no expertise in these areas, so i cannot comment
Branching this discussion into its own topic
On Thu, Dec 5, 2013 at 11:25 AM, Phil Burfitt wrote:
>
> Tim McNamara wrote:
>
>>
>> If you think that Lilypond's web page needs a facelift, then
>> volunteer to roll up your sleeves and help change it...
>>
>>
> Werner Lemberg wrote:
>
>>
>> Do yo
39 matches
Mail list logo
