The problem The Typography panel lets me set a headline font, a content font, a text color, and a link color. It does not let me set size or color for individual heading levels. There is no way to define H1 through H6 and paragraph once and have pages follow it. So every heading gets styled by hand. A ten page site with six headings per page is roughly sixty manual operations to apply a single design decision. Revising that decision means doing it again. Across four sub accounts, the number becomes absurd. Why the standard workaround does not work either When a font size is set on an element in the builder, GHL writes an element specific rule and marks it !important. That means Custom CSS cannot override it unless the selector is specific enough to outrank the platform's own output. Working that out took me several hours of testing with browser dev tools. I also found that the head tracking code field silently truncates somewhere around 2,500 characters, with no error and no warning. The page simply renders in default Arial and you are left guessing. When I called support about this, I was told to change each element manually. What I am asking for In the Typography panel, add per level controls for H1 through H6, subheading, and paragraph, each with: Font family Font size Font weight Line height Color With: Separate values for desktop, tablet, and mobile Availability at the funnel and website level A page level override for exceptions Elements inheriting by default, with an element specific style written only when a user deliberately overrides A "Reset to inherit" control so existing pages can be brought back under global settings The last two points are the heart of it. The current builder bakes a size into every element whether or not the user asked for one. That is why nothing cascades and why Custom CSS has to fight the platform instead of working with it. Why this matters commercially I am building toward offering GHL implementation as a service. The platform's strength is that everything talks to everything else, and I have chosen it over Framer and Webflow for exactly that reason. But the page builder is where an agency spends most of its production hours, and right now it is the slowest part of the stack for the most basic task there is. Every hour spent styling headings by hand is an hour not spent on workflows, automations, or client acquisition, which are the things that keep accounts on the platform. I would also gently note that a great deal of recent development has gone into AI tooling. I understand the strategic reasoning. I would ask that foundational builder capabilities get attention alongside it. AI that generates a page is worth much less when the page it generates still has to be corrected element by element. This request has been open on your ideas board since January 25, 2024. The panel already has the screen space. I would be glad to help test it. Can you please add the additions under the typography? Thank you for considering it.
