Carl Peterson carlopeter...@gmail.com writes:
On Sun, Dec 8, 2013 at 5:55 PM, Carl Peterson carlopeter...@gmail.comwrote:
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 body tag that
2013/12/9 Carl Peterson carlopeter...@gmail.com:
2013/12/6 David Kastrup d...@gnu.org:
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
Il 09/dic/2013 09:22 Janek Warchoł janek.lilyp...@gmail.com ha scritto:
2013/12/9 Carl Peterson carlopeter...@gmail.com:
2013/12/6 David Kastrup d...@gnu.org:
A complete color _scheme_ might be distracting, but it may make sense
to
have a title or side bar or other obvious always
2013/12/6 Federico Bruni 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:
https://code.google.com/p/lilypond/issues/detail?id=3714
Am 08.12.2013 23:23, schrieb Federico Bruni:
2013/12/6 Federico Bruni fedel...@gmail.com 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
On Sun, Dec 8, 2013 at 5:34 PM, Urs Liska u...@openlilylib.org wrote:
Am 08.12.2013 23:23, schrieb Federico Bruni:
2013/12/6 Federico Bruni 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
On Sun, Dec 8, 2013 at 5:55 PM, Carl Peterson carlopeter...@gmail.comwrote:
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 body tag that will allow me to color code each manual.
One
On Fri, Dec 6, 2013 at 3:26 AM, Janek Warchoł janek.lilyp...@gmail.comwrote:
2013/12/6 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com 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)
Am 06.12.2013 09:12, schrieb Janek Warchoł:
2013/12/6 Carl Peterson carlopeter...@gmail.com:
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
2013/12/7 David Kastrup d...@gnu.org:
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
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 davidkbol...@gmail.com:
...
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
On 12/7/2013 9:48 AM, Janek Warchoł wrote:
2013/12/7 David Kastrup d...@gnu.org:
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 Sat, Dec 7, 2013 at 3:42 PM, Phil Holmes m...@philholmes.net 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
2013/12/6 Carl Peterson carlopeter...@gmail.com:
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
Janek Warchoł janek.lilyp...@gmail.com writes:
2013/12/6 Carl Peterson carlopeter...@gmail.com:
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
2013/12/6 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com 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
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
2013/12/6 Phil Burfitt phil.burf...@talktalk.net
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
Federico Bruni writes:
2013/12/6 Phil Burfitt phil.burf...@talktalk.net
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
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 waits
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
Urs Liska m...@ursliska.de 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
On Fri, Dec 6, 2013 at 9:00 AM, James Harkins jamshar...@gmail.com 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
- 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
Phil Holmes m...@philholmes.net 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
- Original Message -
From: Phil Holmes m...@philholmes.net
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
: LilyPond Website Work (was: A thought on Windows Experience)
- Original Message -
From: Phil Holmes m...@philholmes.net
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
On Fri, Dec 6, 2013 at 11:08 AM, Phil Holmes m...@philholmes.net 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
.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
From: Ryan McClure ryanmichaelmccl...@gmail.com
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
From: Ryan McClure ryanmichaelmccl...@gmail.com
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
Urs,
2013/12/6 David Kastrup d...@gnu.org:
Urs Liska m...@ursliska.de 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
Am 06.12.2013 21:26, schrieb Janek Warchoł:
Urs,
2013/12/6 David Kastrup d...@gnu.org:
Urs Liska m...@ursliska.de 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
Branching this discussion into its own topic
On Thu, Dec 5, 2013 at 11:25 AM, Phil Burfitt phil.burf...@talktalk.netwrote:
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:
Hi,
2013/12/5 Carl Peterson carlopeter...@gmail.com:
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,
On 12/5/13 9:43 AM, Carl Peterson carlopeter...@gmail.com 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
On Thu, Dec 5, 2013 at 8:13 PM, Carl Sorensen c_soren...@byu.edu wrote:
On 12/5/13 9:43 AM, Carl Peterson carlopeter...@gmail.com 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
37 matches
Mail list logo
