[prev in list] [next in list] [prev in thread] [next in thread]
List: lilypond-user
Subject: Re: New LilyPond website
From: John Roper <johnroper100 () gmail ! com>
Date: 2016-11-30 23:55:42
Message-ID: CANRGZ5c_2dQPPGV0u=xHGDqBuJ3Ezzj_2q-mU17BtB9gq=2ikA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I am going to put the code in a GitHub repo for now so that I can keep
track of it.
On Nov 30, 2016 6:53 PM, "John Roper" <johnroper100@gmail.com> wrote:
> I am prepared to take my design and start to convert it over to the text
> info generator (at least on the home page).
>
> On Nov 30, 2016 6:29 PM, "Carl Sorensen" <c_sorensen@byu.edu> wrote:
>
>>
>>
>> On 11/30/16 2:58 PM, "Noeck" <noeck.marburg@gmx.de> wrote:
>>
>> >
>> >I was a bit disappointed that the suggestions have narrowed down so
>> >quickly to something so close to the old layout. But perhaps the chances
>> >are better to get somewhere from there than to have ~10 to quickly ~50
>> >completely different proposals.
>>
>> Here's my view of the course of this discussion:
>>
>> 1) John came up with a Wordpress layout. (I never saw that layout,
>> because it has been replaced with the new "just adjust the CSS" lilypond
>> example).
>>
>> 2) Some people expressed appreciation for the new layout; others expressed
>> concerns about the technology. John, in an impressive burst of work
>> created multiple versions responding to people's concerns.
>>
>> 3) Several users discussed preferences for the old design.
>>
>> 4) Some developers chimed in about the desire/necessity to keep the
>> website auto created and pointed out that it would be straightforward to
>> change the CSS.
>>
>> 5) John followed that lead and jumped in with changes to the CSS.
>>
>> It seems likely to me that we are not too far from having new CSS that can
>> be added to the LilyPond source to make some incremental, but significant
>> improvements to the website.
>>
>> Once John has worked on getting the new CSS implemented, he'll be in much
>> better shape to make recommendations for changes that are or can be made
>> consistent with our current infrastructure. Such changes have a very high
>> likelihood of implementation. Since my time being involved with LilyPond,
>> I can't remember a developer who proposed changes in the website that
>> could be implemented in our current framework failing to get those changes
>> adopted.
>>
>> Changes that require shifting large parts of our current source (and by
>> that I mean documents, not code) to some different infrastructure will be
>> met with skepticism by the development community, I believe. Someone who
>> wants to have such changes made will need to shoulder most (or all) of the
>> burden to make those changes. But if someone is willing to do that, and
>> the new infrastructure will support our translation process as well or
>> better than our current infrastructure, I would expect those changes to
>> eventually be implemented.
>>
>> I hope John doesn't feel like he's had a negative response. I believe
>> he's had a response that points out the minefields he needs to avoid in
>> order to get the website changed. And it looks to me like he's jumping in
>> and navigating the minefields, which I think is great.
>>
>> Thanks,
>>
>> Carl
>>
>>
[Attachment #5 (text/html)]
<p dir="ltr">I am going to put the code in a GitHub repo for now so that I can keep \
track of it.</p> <div class="gmail_extra"><br><div class="gmail_quote">On Nov 30, \
2016 6:53 PM, "John Roper" <<a \
href="mailto:johnroper100@gmail.com">johnroper100@gmail.com</a>> wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I am prepared to take \
my design and start to convert it over to the text info generator (at least on the \
home page).</p> <div class="gmail_extra"><br><div class="gmail_quote">On Nov 30, 2016 \
6:29 PM, "Carl Sorensen" <<a href="mailto:c_sorensen@byu.edu" \
target="_blank">c_sorensen@byu.edu</a>> wrote:<br type="attribution"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br> <br>
On 11/30/16 2:58 PM, "Noeck" <<a href="mailto:noeck.marburg@gmx.de" \
target="_blank">noeck.marburg@gmx.de</a>> wrote:<br> <br>
><br>
>I was a bit disappointed that the suggestions have narrowed down so<br>
>quickly to something so close to the old layout. But perhaps the chances<br>
>are better to get somewhere from there than to have ~10 to quickly ~50<br>
>completely different proposals.<br>
<br>
Here's my view of the course of this discussion:<br>
<br>
1) John came up with a Wordpress layout. (I never saw that layout,<br>
because it has been replaced with the new "just adjust the CSS" \
lilypond<br> example).<br>
<br>
2) Some people expressed appreciation for the new layout; others expressed<br>
concerns about the technology. John, in an impressive burst of work<br>
created multiple versions responding to people's concerns.<br>
<br>
3) Several users discussed preferences for the old design.<br>
<br>
4) Some developers chimed in about the desire/necessity to keep the<br>
website auto created and pointed out that it would be straightforward to<br>
change the CSS.<br>
<br>
5) John followed that lead and jumped in with changes to the CSS.<br>
<br>
It seems likely to me that we are not too far from having new CSS that can<br>
be added to the LilyPond source to make some incremental, but significant<br>
improvements to the website.<br>
<br>
Once John has worked on getting the new CSS implemented, he'll be in much<br>
better shape to make recommendations for changes that are or can be made<br>
consistent with our current infrastructure. Such changes have a very high<br>
likelihood of implementation. Since my time being involved with LilyPond,<br>
I can't remember a developer who proposed changes in the website that<br>
could be implemented in our current framework failing to get those changes<br>
adopted.<br>
<br>
Changes that require shifting large parts of our current source (and by<br>
that I mean documents, not code) to some different infrastructure will be<br>
met with skepticism by the development community, I believe. Someone who<br>
wants to have such changes made will need to shoulder most (or all) of the<br>
burden to make those changes. But if someone is willing to do that, and<br>
the new infrastructure will support our translation process as well or<br>
better than our current infrastructure, I would expect those changes to<br>
eventually be implemented.<br>
<br>
I hope John doesn't feel like he's had a negative response. I believe<br>
he's had a response that points out the minefields he needs to avoid in<br>
order to get the website changed. And it looks to me like he's jumping in<br>
and navigating the minefields, which I think is great.<br>
<br>
Thanks,<br>
<br>
Carl<br>
<br>
</blockquote></div></div>
</blockquote></div></div>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic