Foundry Update: Introducing Typeface font management stack
We've been steadily updating Foundry since its initial release back in July of 2016. Over that time we've made lots of improvements, added a slew of new stacks, and squashed plenty of bugs.
With this new release we're at it again. Version 220.127.116.11 brings with it a couple of new stacks, lots of improvements as well as bug fixes. It also paves the way for some more additions to the Foundry family later this year.
Before we dive into the two new stacks for Foundry I will quickly say that you can find the full release notes for this version over on the Release Notes page on the Foundry site. It details all of the changes, additions, bug fixes and whatnot so you can always stay up to date on Foundry’s evolution. With that said, let’s dive into the two new stacks in v18.104.22.168…
We’ve known for a little while now that font management in Foundry could be better. Foundry shipped with the ability to use standard web safe fonts within the main Foundry Control Center stack and other select stacks even allowed for the use of Google Fonts through their settings. From user feedback we knew the way things were setup wasn’t really an elegant enough, easy-to-use solution and didn’t provide enough flexibility.
So we set out to build a stack that would allow you to manage your web safe and Google Fonts, as well as Adobe’s Typekit fonts, all in one location and then call upon those fonts from other stacks within Foundry.
Typeface allows you to add font families as child stacks inside of it, and then assign that font family to a typeface. That typeface can then be chosen in other stacks, like the Header or Paragraph stacks, for instance. This method makes sure that your fonts are each loaded just once per page as well as streamlines assigning said fonts to elements on the page. It also opens up a lot more options for Foundry as a whole, as well as lets us more easily integrate with other Foundry stacks without worrying about duplicating font loading.
We’ve created some tutorial videos showing how Typeface works (the overview video is below) as well as how to use Google Fonts and Adobe Typekit within the Typeface stack. Be sure to watch these videos, even if you’re familiar with Google Fonts or Adobe Typekit, as they not only give you an idea of how these services work, but these videos also detail things you’ll need to know when using them in the Typeface stack.
Typeface will make customizing Headers, Page Headers, Paragraphs and more so much easier. You’ll now find Typeface options within these stacks, and more, which allow you to use the fonts you’ve defined in Typeface in these other stacks.
We’ll also be tying this feature into future stacks, where necessary, as well. For more information on Typeface’s settings, be sure to have a look at the Typeface documentation page.
This is another stack I’ve had requests for over time. The Site Map stack adds a very simple, but helpful, site map to any Foundry page. You can easily give your visitors a top-down view of the structure of your site. The stack abides by RapidWeaver’s page settings, so if you hide a page from the navigation for instance, it will be hidden in the Site Map as well. Learn more about Site Map’s features on its documentation page.
MORE TO COME
With this update we’ve paved the way for future Foundry stacks. We’ve worked on the core code in preparation for a set of Foundry add-ons that are in the works. This set of add-ons will be out later this year. A date for this pack is not yet planned, as things are still in flux. But stay tuned to the blog and I’ll let you know as we get closer.