css style applied for title page

[alsed]

• stylesheet applied extensively for the title page.
• stylesheet applied for the title of the toc page

I'm aware that the guideline stated that no aesthetics changes be proposed. In this regard:

• No new fonts nor css have been created, only the current css style is applied.
• The change is minimal, in order to preserve the overall document presentation.
• The proposal also tried to add consistency to the document style.
• This is a PROPOSAL, the person in charge must determine whether or not this is consistent with the design principles.
• I DO believe this changes, while not totally correct, contribute to the presentation of the document.

[BeckyDTP]

This suggestion is not the best, because it would force the need to repeat this change after each update of the HTML version of the Table of Contents. To be consistent with the h1 style of the entire publication, it would be better to modify the style for the div.sgc-toc-title class and load the appropriate font directly into the style assigned for the TOC (sgc-toc.css).

@font-face {
    font-family: 'SmallCaps';
    font-weight: bold;
    font-style: normal;
    font-variant: small-caps;
    src: url(../Fonts/Fontin-SmallCaps.otf);
}

div.sgc-toc-title {
    font-family: 'SmallCaps', sans-serif;
    font-size: 2em;
    font-weight: bold;
    font-variant: small-caps;
    text-align: center;
    margin-top: 0.0em;
    margin-bottom: 0.5em;
}

[kevinhendricks]

Agreed. That is what the sgc-toc.css file is for.

Happy to merge in your change once you adapt it following BeckyDTP comments.

[alsed]

Based on this comment, is it also better for the title page to maintain the class "author" and modify the font in the proper css file?

[dougmassay]

Is our html TOC auto-generated from the NAV using Sigil? It makes sense if so. I guess I just never put two and two together. I'll need to remember that when adding chapters before releasing. Everything else about building/releasing the guide is fairly automated.

[kevinhendricks]

Yes you recreate the HTML toc from the nav, then I always run the epub3 tool to update the toc.ncx and guide from the nav as well. That way even old epub2 e-readers still work.

[dougmassay]

Makes sense. I don't think I've ever added a new chapter/xhtml file. I was worried for a second that I had no way of generating the ncx/TOC when automating new releases of the Guide with GitHub Actions. But there's no need. These things would happen locally and be pushed to the Guide's repo. All good.

[alsed]

Changes made as requested

[dougmassay]

I'm ok with the style changes (especially after the new commit), but won't the title and version lines being changed from p to h1 cause new entries to be added to the generated TOC, ncx, nav, etc... ? Or am I missing something?

Unless I'm missing something

[alsed]

If additional changes are needed, let me know.