Ben Franklin made this warning. His book, Increase of Mankind (1751), shows how rising numbers undermine wages. His last speech to the U.S. Constitutional Convention closed the argument. Constitutional government, he said, "is likely to be well administered for a course of years, and can only end in despotism...when the people shall become so corrupted as to need despotic government, being incapable of any other."

↓

Post Perfect Trial effort at a better blog post. This is an h1 heading centered. I’m using multiple lines long to judge line height.

This POST PERFECT effort is intended to find a group of settings that work well together.

This is based on your FUT WebHostInfo HostGator 2022.docx file at “My Post History.” MY POST HISTORY there should ultimately summarize settings that work here, hopefully enabling creation of identical posts.

Heading h2: What IMAGE PLACEMENT is best? Again this heading h2 uses multiple lines to try to get multiple lines to look decent.

SECTION padding at 0px does move the SECTION IMAGE upward by about a quarter of an inch. Will this line of text look good with a second line?

ROW padding at 0px does move the ROW IMAGE upward by about another quarter of an inch.

MODULE margin-top at -100px (-6.25em) moves the image immediately below the site’s menu.

Perfect!

Heading h2 What HEADING SETTINGS are best?

Divi Theme Customizing > General Settings > TYPOGRAPHY seems to control until you make changes within a particular module’s DESIGN TAB.

HEADING STYLES must obviously be adjusted one DEVICE MODE at a time.

PC MODE settings that seem to work:

BODY TEXT is set here as fontweight: regular; font size:2em; line height: 1.2em;

My h1 above was made using the following settings: alignment: center; fontweight: semi-bold; font size: 2em; line height: 1em. Yes 1em, not 1.2 em of the TEXT line height.

H2 is semi-bold, 1.75em, 1em,

H3 is semi-bold, 1.5em, 1em,

H4 is semi-bold, 1.25em, 1em,

H5 is semi-bold, 1em, 1em.

These seem to look acceptable.

TABLET settings that seem to work:

BODY TEXT is set here as alignment: left; fontweight: regular; font size:2em; line height: 1.2em;

My h1 above was made using the following settings: fontweight: semi-bold; font size: 2em; line height: 1em. Yes 1em, not 1.2 em of the TEXT line height.

H2 is semi-bold, 1.75em, 1em,

H3 is semi-bold, 1.5em, 1em,

H4 is semi-bold, 1.25em, 1em,

H5 is semi-bold, 1em, 1em.

These seem to look acceptable.

Identical MOBILE phone settings seem to work.

BODY TEXT is set here as alignment: left; fontweight: regular; font size:2em; line height: 1.2em;

My h1 above was made using the following settings: fontweight: semi-bold; font size: 2em; line height: 1em. Yes 1em, not 1.2 em of the TEXT line height.

H2 is semi-bold, 1.75em, 1em,

H3 is semi-bold, 1.5em, 1em,

H4 is semi-bold, 1.25em, 1em,

H5 is semi-bold, 1em, 1em.

These seem to look acceptable.

Heading h3: Again this heading must be more than one line long or else we won’t be able to see the effect of the LINE HEIGHT command.

Heading h4: OBSERVATIONS relating to how you work with and differently characterize these various h & p declarations.

Heading h5: Divi’s PC VIEW isn’t WYSIWYG, but Divi’s TEXT SETTINGS > CONTENT TAB > TEXT VIEW seems more WYSIWYG (though not accurate to the EXIT DIVI BUILDER / BROWSER VIEW). One example is the SPACE AFTER PARAGRAPH.

Here the paragraph doesn’t have a space between itself and its preceding header equal to the space that follows the paragraph (which is customary). Can this be varied?

Why is the gap between paragraphs so much greater than the gap between a heading and a paragraph? Both should be the same size.

Note again that we don’t see WYSIWYG exactly until you EXIT DIVI BUILDER.

Heading h5: Cursor location that works to recharacterize a paragraph as any form of h or p.

Remember that an h or p setting requires ONLY THE CURSOR to be located in a line. When I try to save a whole paragraph before scrolling up to find the paragraph / header selector, the selection de-selects.

The cursor can be anywhere in the line. The cursor need not be at the beginning or the end if the line, although these positions (and anywhere in between) will work equally well.

Heading h5: This is my last heading format and should appear as smaller than my text size. It still stands out.

Problem # 1: These headings look good in DIVI CONTENT TAB VIEW. How about in BROWSER VIEW?

Problem # 2: Do I care about the initial paragraph space after a heading?

Heading h2: READMORE TEXT SETTINGS seem to work well when I’m editing in DIVI, but not when I open POST PERFECT as a POST. Can I fix this?

Can I fix this? Jeans ADDITIONAL CSS COLUMN addition of the following code seems to work well. h1 {
padding-bottom:30px!important;
}

Post Perfect form backup #2

Post Perfect Trial effort at a better blog post. This is an h1 heading centered. I’m using multiple lines long to judge line height.

Heading h2: What IMAGE PLACEMENT is best? Again this heading h2 uses multiple lines to try to get multiple lines to look decent.

Heading h2 What HEADING SETTINGS are best?

PC MODE settings that seem to work:

TABLET settings that seem to work:

Identical MOBILE phone settings seem to work.

Heading h3: Again this heading must be more than one line long or else we won’t be able to see the effect of the LINE HEIGHT command.

Heading h4: OBSERVATIONS relating to how you work with and differently characterize these various h & p declarations.

Heading h5: Divi’s PC VIEW isn’t WYSIWYG, but Divi’s TEXT SETTINGS > CONTENT TAB > TEXT VIEW seems more WYSIWYG (though not accurate to the EXIT DIVI BUILDER / BROWSER VIEW). One example is the SPACE AFTER PARAGRAPH.

Heading h5: Cursor location that works to recharacterize a paragraph as any form of h or p.

Heading h5: This is my last heading format and should appear as smaller than my text size. It still stands out.

Heading h2: READMORE TEXT SETTINGS seem to work well when I’m editing in DIVI, but not when I open POST PERFECT as a POST. Can I fix this?

0 Comments

Submit a Comment Cancel reply