fix(cxl-lumo-styles): limit secondary font style in ul to .entry-content

[freudFlintstone]

As requested in cxl-wpstarter PR

Tested locally:

[github-actions]

size-limit report 📦

Path	Size
packages/cxl-ui/pkg/dist-web/cxl-ui.js	66.98 KB (+0.02% 🔺)
packages/cxl-ui/pkg/dist-web/cxl-ui-jwplayer.js	11.87 KB (0%)
packages/cxl-ui/pkg/dist-web/cxl-ui-playbooks.js	28.14 KB (+0.05% 🔺)
packages/cxl-ui/pkg/dist-web/vendor.js	135.58 KB (0%)
packages/cxl-ui/pkg/dist-web/cxl-ui-jwplayer.js, packages/cxl-ui/pkg/dist-web/cxl-ui-playbooks.js, packages/cxl-ui/pkg/dist-web/cxl-ui.js, packages/cxl-ui/pkg/dist-web/manifest.js, packages/cxl-ui/pkg/dist-web/unresolved.js, packages/cxl-ui/pkg/dist-web/vendor.js	243.72 KB (+0.02% 🔺)

[lkraav]

Yeah, in theory it will improve current state.

But we just discussed things with @heshfekry and may be opting for a deep simplification by "reset all to single typeface, expand from there".

Let's see what the decision will be there, this PR might then need to morph into just removing usage (but not definition) of secondary typeface.

[pawelkmpt]

@lkraav what about global p style? It was also set to secondary font family and one of the pieces affected is course about section:

[pawelkmpt]

Task linked: CU-86aytq9gd Fix paragraph vs element fonts

[lkraav]

what about global p style

Yep, highly likely also needs to be contained with .entry-content, but we discussed the big elephant in the room in a @heshfekry huddle today

• in WP almost everything is a content page
• thus has .entry-content element
• we might need some sort of a content page categorization system, if we are to continue with multiple typefaces: for example, out of post type page, only sales pages should probably have serif content.
• ...or we try "big single-typeface sans-serif-only reset", and start over from there looking into where and how "secondary" or "serif" can be implemented for various glorious benefits

[pawelkmpt]

what about global p style

Yep, highly likely also needs to be contained with .entry-content, but we discussed the big elephant in the room in a @heshfekry huddle today

It is already. First line could be dropped @freudFlintstone.

 {
  font-family: var(--cxl-lumo-font-secondary);
  .entry-content & {
    font-family: var(--cxl-lumo-font-secondary);
  }

• in WP almost everything is a content page
• thus has .entry-content element

Yeah, it's tricky.

• we might need some sort of a content page categorization system, if we are to continue with multiple typefaces: for example, out of post type page, only sales pages should probably have serif content.
• ...or we try "big single-typeface sans-serif-only reset", and start over from there looking into where and how "secondary" or "serif" can be implemented for various glorious benefits

Will be next step. For now let's just focus on patching recent changes.

[freudFlintstone]

@pawelkmpt how are you getting that? I only see the new one:

If that's from your IDE? If that's a merge, there's a problem with it

[pawelkmpt]

If that's from your IDE? If that's a merge, there's a problem with it

I linked to the piece of code in

@lkraav what about global p style? It was also set to secondary font family and one of the pieces affected is course about section:

I played with it myself and it seems more complex than ul, ol.