McLuhan Heading Styles


#1

PB 5.4.1, McLuhan 2.4.1
The header styles do not appear to have a gradual change in size as was expected by academics for H1-H3:
Screenshot_2018-07-17%20test%20page

However, the Open Textbook theme has the expected gradual font size in the headings hierarchy (H1-H3):
Screenshot_2018-07-17%20TP


#2

Addendum - WordPress Theme - Twenty Seventeen Headings Style:
Screenshot_2018-07-17%20Twenty%20Seventeen%20WordPress%20org


#3

We built McLuhan based on specifications from the client which only included font sizes for headings (<h1>) and sub-headings (<h2>). We’re open to revisiting this in a future release.


#4

a <p> bigger than a <h2>, makes complicate to understand the hierarchy of the content.


#5

The academic heading sizes may align partially with the Open Textbook theme, and completely with the Twenty Seventeen theme. What parts of the CSS do I need to change, to avoid academic authors manually coding a solution?


#6

As an aside: You keep mentioning “academic” but as Ned mentioned, we buil McLuhan based on specifications from the client. The client was ecampusontario. Basically, all academics in the province of Ontario.

Is there a recognized academic standard we’re not aware of?

Regards,


#7

I believe visual aides (i.e., cues) to content separation will bring greater meaning to the consumer (e.g., learner); therefore logically an outline of headings of gradual size relative to level in the hierarchy will enrich textural communications.

As a volunteer helping academics in migration of analog content to a digital environment, I support their request for an expected gradation in heading size. Unlike a word processor, an author cannot select a heading in the PB editor and expect a different font size, as the theme controls the presentation rather than the editor (PB theme template vs word processor basic configurable template).

Hence, I need to know which parts of the McLuhan CSS I need to change to fix the issue, or return to the Open Textbook Theme.

Thanks.


#8

Maybe this Tweet from @SteelWagstaff can help you?

It leads to this code snippet.

More info on how you can use that code snippet here:

https://guide.pressbooks.com/chapter/customizing-your-exports-with-custom-styles/

If you really want to go down the road of fixing McLuhan then you should create a child theme. Your theme would inherit McLuhan then you would make your changes there.That’s a lot more work than pasting code into the custom styles editor. In fact, minus the extra features, this is exactly how the Open Textbook theme works:

Examples child themes you can look at for dev purposes.

Regards,


#9

Hey Steve, the heading elements can be selected and made subject to CSS overrides by using the following pattern: .part h2, .chapter h2, .back-matter h2. Replace H2 with whichever heading element you want to target [H1 through H6 are defined in the parent theme]. The .part, .chapter and .front-matter .back-matter selectors help you identify the heading element in the various post types created by Pressbooks.


#10

Thank you for the CSS

Status: PB 5.4.2 McLuhan 2.4.1

heading.css - added h1 2.25rem (otherwise h1 would be smaller than rest of headings)

However, the editor displays:

The resulting web view:


#11

In Pressbooks 5.4/McLuhan 2.4 we changed the markup for new educational textboxes so that they don’t use an <h3> for the textbox title. So new textboxes that you add should not have this issue. To resolve it for existing textboxes, maybe try…

- .part h3, .chapter h3, .back-matter h3, body#tinymce.wp-editor h3 {
+ .part > h3, .chapter > h3, .back-matter > h3, body#tinymce.wp-editor > h3 {
   font-size: 1.75rem;
}

#12

Thanks for the CSS, perhaps find and replace is another option in conversion of textboxes to McLuhan?


#13

Pressbook’s search and replace is only for things found in the_content

Inline CSS in the_content is strongly discouraged.

But yeah if that’s where your CSS is… then searching and replacing, with regular expressions, can be powerful.

I don’t think this applies here.


#14

Steve–the new markup appear to be structured like this: <div class="textbox textbox--key-takeaways"<header class="textbox__header"><p class="textbox__title">Key Takeaways</p></header><div class="textbox__content"> (that’s an example for the Key Takeaways textbook, some of the classes will be different for different textbox types.

What’s the html markup for one of your old textboxes inserted pre PB 5.4/McLuhan 2.4 (with the <h3> elements in them)? If you include that here, I might be able to help you think up a search/replace command that could find and replace them with the current markup for educational textboxes …


#15

thanks - already completed - I applied your heading CSS fix and works fine. With regards to boxes, there were only a few boxes so I modified HTML by searching within webpages, rather than global find/replace. Ah the evolution of standardized boxes in themes.