Issue 36480048: Enable manual-specific styling of documentation; issue 3714
DescriptionEnable manual-specific styling of documentation; issue 3714
Providing capability for the CSS stylesheet to "see" which manual is being used and the development status of the manual for styling purposes. Adds classes to
the HTML <body> tag based on the filename of the manual, as well as a
(currently) hard-coded value for development status. Comments follow based on
individual patches, in reverse order
==
Add comments to lilypond-texi2html.init
Adding inline comments to lilypond-texi2html.init to explain the added lines of code in the file to enable the manual-specific CSS styling.
Also cleaned up the code indentation levels.
==
CSS changes to color-code major manuals
Added styling to use a manual-specific class in the <body> tag to color code each of the major manuals.
Now:
* Learning Manual: Green book
* Notation Reference: Blue book
* Usage Manual: Yellow book
* Extending: Red book
* Internals Reference: Purple book
* Contributor's Guide: Black book
==
Add classes to <body> tag of documentation files
To facilitate request from lilypond-user to facilitate differentiating among the various manuals, appending CSS classes to the <body> tag of the documentation files so that the main CSS stylesheet can be modified to look for those classes to specifically style each manual and development status.
The present solution for indicating development status is a hardcoded line in Documentation/lilypond-texi2html.init.
Patch Set 1 #
Total comments: 1
Patch Set 2 : Remove duplicate definitions from lilypond-manuals.css file, per review #Patch Set 3 : issue 3714, adjust sidebar colors for legibility and contrast #Patch Set 4 : Issue 3714, follow-up changes to CSS colors for manuals based on feedback from reviewers. Changing … #
MessagesTotal messages: 10
|
||||||||||||||||||||||||||||
