Hi

Thanks for contacting us. Is it possible to give me any screenshot of your issue?

-Regards.

It's not really an issue, per se. Maybe a feature request?

![https://ibb.co/5BsGZt9]

As you can see, you cannot change the default Section Title font-face.

But from Helix Ultimate, you cannot choose a custom font for H1-H6 (only system or Google).

This is an amazing new feature and so glad it has been added.

Hi. Adding this feature to SPPB is a populism for the sake of newcomers to the Web industry. And has nothing to do with the right work with the site in the aspect of performance. Professionals would prefer to have this at the template level but not inside SPPB. In my opinion, any possibilities of choosing fonts should be completely removed from SPPB. But this would blow up public opinion. :)

Helix needs this feature, not SPPB.

(IMO)

I cannot choose the font for a section heading within SPPB; instead, it pulls the font from the template

Completely turn off this in Helix to get the opportunity to use your font in SPPB. Since the setting of fonts in Helix is the highest priority (as it should be).

I hope this is what will help you understand that the fonts should be used at the global level, but not inside a separate component as SPPB. Since usually there are other pages from other components for which typography is also required. Website should use a maximum of 3 fonts (goob point is no more than 2 fonts), based on performance and good tone in design.

Therefore, with all the charms of this feature, I consider it not suitable for use. Unless in rare cases when you make a landing page and there is nothing else on the site (things like Header, Footer, articles and ect).

I apologize for my spoon of tar. :)

Hello Pavel,

I whole-heartedly agree with you that the fontbook should be on the Helix level (but I can also understand having it on the SPPB level for those who are not using a Helix-based template). As a web developer/designer of 15+ years, I am a hard-core proponent of the 2-font max rule.

Unfortunately, toggling the heading features within Helix does not reveal an option to choose fonts within the Title tab of the Section settings. The only solution to this problem would be to either add the fontbook feature to the Helix framework or add the option to choose fonts for Section Titles within SPPB.

Wouldn't SPPB read the template settings from whatever template or custom css is installed? This I agree with Pavel that the template should prevail - and that instead a provision for a custom header/font classes be what appears in SPPB.

I think this thread is getting off topic. Yes, template should prevail, but we're talking about utilizing the custom fontbook feature that has been recently added to SPPB.

In other words, yes, I am requesting to add the feature to utilize custom fonts via a fontbook to the Helix framework. But until then, all I'm asking for is the option to choose the font for the section heading, since I cannot set H1-H6 to my own custom, uploaded font via Helix at the moment (not a system or Google font).