A system for book sections enabling section labelling and distinct page numbering

[dbolack-ab]

This is one take on how to handle the notion of a brew having multiple, distinctly numbered sections in a way that both the CSS and snippets can track the page number resetting.

This system works by adding a single word parameter to the \page token. This value is added to the class list. This allows both a predefined list and the users to create their own.

These classes should hold no CSS properties and exist to act as triggers to reset the page counter ( phb-page-numbers - which should probably be renamed ) and reset the Section Label and the numbering type for the page counter (Roman numerals, decimal, etc - based on the LI numbering types)

This system uses .(sectionname):nth-of-type(1) for counter resets and .(sectionname) to override two global CSS variables where (sectionname) current defaults to one of index, appendix, chapter, frontmatter, and index.

Current design weaknesses that aren't addressed

• There is no way to track multiple indexes or appendixes and label accordingly ( Appendix A, pg 7 )
• Assumes each section type is used once
• Does not enforce section order
• Behaves the same as the present scheme if the first line of the brew does not set a section style
• Still requires the user to insert the {{pageNumber }} bug.

Strengths:

• SHOULD work on both the CSS side of the document and the snippets side by binding the counter resets to a token
• Requires nothing of users not wanting to use it.
• Easy extension via themes
• Allows user extension via the brew styles tab

Solves:

Issue #2826

[Gazook89]

The deployment doesn't seem to work at this point. It doesn't load the stylesheet and some other error. Crashes if I type in the editor as well.

I haven't taken a look at the code yet so don't have much more to say, just a heads up.

[dbolack-ab]

The deployment doesn't seem to work at this point. It doesn't load the stylesheet and some other error. Crashes if I type in the editor as well.

I haven't taken a look at the code yet so don't have much more to say, just a heads up.

I haven't updated this one in a bit, I'm not surprised it has some issues. I'm going to move it back to draft until I can catch it back up.