Font Management doesn't work

Similar to the older topics here, I’m trying to leverage what Theme Pro calls “Font Management” which I assume means I can global manage my fonts instead of having to manually manage them for every component using the same H1-6 tags.

Here I’ve set up a basic adjustment to attempt this but my Headline component which is set to H2 didn’t do anything. I then even attempted to set it’s font values to “inherit” and that still did nothing.


I don’t understand the point of the Font Manager feature if it doesn’t manage fonts in this way. I may be speaking to early but from what I’ve seen of other similar post in this forum, if the required action is to code CSS for this basic global expectation (literally every site requires global typography) then I may have overestimated the ability of this theme. Praying that is not the case.

Hey Nicholas,

The Font Manager is only for the management of fonts. Our themes do not have a global typography feature where users can customize every aspect of typography. The Typography settings in the Theme Options are for the old theme Stack system and are limited for the chosen Stack design. The Headings Typography settings, for example, is for the theme’s templates.

In your screenshot, you’re using the Headline element. When using Cornerstone, you are no longer limited by the Theme Options. You are in control of the whole website design. Therefore, you should use the Component Builder along with the Layout Builder to build your own design and building system. For example, you create different styles of the Headline element. You save each of them as a component so you can your own styled elements. This way, the building system is better than a regular “global typography” options of a regular theme.

Hope that helps.

Hey Christian,

Thanks for that thoughtful explanation. I watched the video and I see how the Component Builder component can be powerful for custom building, but I have to be honest, it seems like gap catcher for everything Theme Pro / Cornerstone marketing made me believe was included. To encourage any one to build a site with the " Extensive Element Library" is a giant waste of time because they will literally have to style every element again and again. Not to mention, God forbid they get feedback that requires a change.

So really this page builder is a low-code component builder, meaning any user needs to be comfortable coding on a basic level. I can personally manage this but really don’t like being sold a lie. At this point I’m hoping that the Component Builder is just the temporary solution while the product team continues to finish building what the sales team has already sold. Please remind them that typography is like a basic aspect of web development. To be the best tool you have to encourage the best practices.

Thanks for the help with this, maybe next week I can build a website once I finish designing and configuring all these basic components (ie. headers, body content, ctas and buttons, etc.). Maybe there is a way to downgrade to the “old theme stack system” which is still limited by common sense? Sorry for the frustration but on top of the front-end mislead I’m surprised that this is promoted as a “feature” and not just the temporary solution it should be. My confidence in the entire ThemeCo approach is a bit shook right now.

Tell me this… is it possible to use dynamic content within the standard or custom components? For example, in my footer I would like to set the background color to use the Globals > Footer Background. I tried things like:

  • {{dc:globals:footer-background}}
  • --globals-footer-background

Unfortunately neither of these seemed to work. I couldn’t find an answer in the Dynamic Content documentation either so I’m guessing the answer no but I’m still holding out hope that there is some value to having a globals section at all.

For the renew stack the footer background can be accessed through {{dc:theme:x_renew_footer_background}}. In Dynamic content you can view the list of options through Theme Option > Option.

image

The way you have set the theme option for the “Headings” theme option seems correct. If it’s not changing the font family on your headline element send us a site to look at and we’ll get a fix for you.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.