[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: website: texinfo macros for both ID and classes
From: |
Paul |
Subject: |
Re: website: texinfo macros for both ID and classes |
Date: |
Mon, 5 Dec 2016 13:13:26 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 |
On 12/05/2016 12:35 PM, Graham Percival wrote:
On Mon, Dec 05, 2016 at 11:49:27AM -0500, Paul wrote:
For the website I'm thinking about adding a macro that can create a div with
both an ID and classes.
Why? What problem would this solve?
That there's no way to create a div that has both an Id *and* one or
more classes. Currently you'd have to create two nested divs one with a
class and one with an id (ugh).
This would be good to have in general and more intuitive for
those used to html.
I'm not convinced.
As someone who knew html and went through the process of figuring out
how to contribute to the LilyPond website, I would have found it more
intuitive and useful to have. There was a point where a div with both
Id and class was needed and there was no way to do it even though this
is the most basic and common thing in html.
I'm just trying to smooth out a point of friction that I encountered,
but sure, there are probably other priorities.
Before changing the underlying texinfo macros, much less the build
system or language used (which is not what Paul is suggesting, but
I know that those ideas are out there), I'd like to see somebody
make an honest effort at working on the CSS.
Well, I have already been doing that and plan to continue to work on the
website as my time allows.
In particular, to make the website look acceptable on small
screens. This would take 2-5 hours, depending on how familiar
that person is with CSS and web browser testing.
I don't think that's too much to ask. If nobody is prepared to
even do that much, then we certainly don't want them to spend time
and effort on larger redesigns that may never be completed. I'm
available to mentor this task.
I can't take this on at the moment given my other constraints and
commitments. (I suspect it would take more than 2-5 hours and might
involve more than changing the CSS, but maybe I'm overestimating it.)
Cheers,
-Paul