Open srambach opened 1 month ago
After discussion between @srambach @mcoker and @lboehling -
There is a long term goal to differentiate type sets for functional components, vs editoral text vs expressive elements like a big page banner.
There is a short term goal to increase the font size on the long form text on .org.
There are a couple of options to accomplish the short term goal -
For now, let's do this:
This can be a spike for core, see if it’s feasible to get in for v6 final release and added as a beta enhancement to content component. If it’s too much to squeeze in to v6 final, we can just make these changes on org and plan to push it upstream to the content component after the v6 release
A users has noted that overall, the text size in PatternFly has decreased. This is in line with an overall adjustment to font sizing coming from the larger design community. https://github.com/patternfly/patternfly/issues/6830 gives details and some a11y concerns were addressed in https://github.com/patternfly/patternfly/pull/6846, which introduces rem units to allow text resizing.
We have identified that there are tokens intended for a larger long-form text, but the large size is currently not used outside the text-size utility class.
We need to determine if the org site should adjust itself to use the larger text token or use a utility class; if the content component should be modified to use the larger text for body text, or if a large variant of body text should be created.