Yuzool Navigation Problem... Custom Font Issue

Since I still have a lot to learn, this could all be my fault :slight_smile: However, I’m having a very hard time getting custom fonts to show up for the nav menu. I’m using Foundry, in case it matters. For the menu’s font selection, I selected ‘Custom’ and proceeded to type in the name of the Google font I would like to use. More often than not, it doesn’t work. I double-checked the spelling and everything was fine. Is this a glitch or a newbie mistake?

Thanks in advance.


The Google font you wish to use has to be in scope or downloaded in advance of you referencing it in the stack. Entering a Google font name into the custom textbox tells the stack which font name to try to use but the stack, as far I can tell, does not insert the ‘call the Google fonts CDN and download the font named xxxx’ part.

Easily overcome though because you can just insert the call to Google to get the font yourself. Just put it in the ‘head’ code section of your project. Like this:

Now that project is good to go with the ‘Gugi’ font:

You can peruse and generate the links you need here:

Hope this helps.

1 Like

That was incredibly helpful! And now for a slight rant and a question :slight_smile:

I’ve been trying to immerse myself into Rapidweaver lately. As someone coming to this from a design background as opposed to a coding/programming background, I’ve noticed that sometimes there seems to be a lack of ‘standardization’ with regards to the way some stacks work or are laid out in the settings window. This case was a perfect example - I have used stacks that call for custom fonts before; they’ve always ‘called out’ to Google to retrieve the font. I spent a long time yesterday rebooting my computer, double-checking my internet connection, watching the ‘tutorials’ on Yuzool’s documentation page (more feature description than tutorial, but that’s all that I could find) before I came to the forums. I can’t be the only design-oriented / non-coder person on here… Was this laziness? Sloppiness? Or are we expected to know these things even though the stacks and Rapidweaver, in general, are supposed to be a mostly WYSIWYG approach to website building? If the fix can be built in I say (@yuzool) FEATURE REQUEST. Seems simple, but I’m guessing :slight_smile:

I’ve used stacks that had adjustments for different parameters, but what I was doing wasn’t labelled in the settings - I’ve had to change their numerical value and see what would happen in preview mode just to know what I was controlling. I get that no one wants to scroll a lot, but not labelling stuff isn’t a viable alternative. And yes, I will eventually learn these little tricks (like what you just showed me - thanks again)! it’s just hard to be excited about working with the software if it’s riddled with these little landmines of sloppiness. This is different than me not knowing the software well. I just figure that the same thing (in this case, getting a font from Google) should work the same way every time. If there’s a reason why it doesn’t, that should be pointed out and adequate instruction given.

Just a fantasy, but I think Isaiah should have some kind of ‘Stacks Camp’ where developers come together to learn or create a series of standard with regards to how they deal with common tasks. And don’t get me started on how stacks are tagged in the viewer window - nightmarish if you own a lot of stacks! Alas, just a fantasy - or is it :wink: Hint hint!

Rant over - I don’t know if I feel better, but I certainly practised some typing :slight_smile: And now my question - how do I get from here (newish, eager, learning) to where I know something like you just showed me? I’ve spent a decent amount of time with tutorials - from Rapidweaver Classroom to Realmac’s own Rapidweaver tutorials to the in-depth tutorials that great developers put out (Adam Shiver @ Elixir for Foundry, for instance) and haven’t really come across anything remotely like the info you gave me. How did you get to where you are? Am I going to have to learn code? I’m sure it would help, but it runs a bit counter to what the software is seemingly about.

Thanks for your help, and thanks for listening!



Is worth noting that a lot of stacks have useful tooltips when you hover over the different settings (certainly for settings that require a bit more detail) but you are right that the quality (or even existence) of things like this can vary greatly between developers. It sounds like you have gone for Foundry though which is a great choice. Adam’s documentation, support and tutorial videos are the best there is.

The key to getting better is just practice though - building your own site and trying to recreate what you see elsewhere. Trial and error is really the best way to learn. Picking up (and dissecting) some example projects are a good starting point too. And whenever you get stuck then there is Google and the different RW forums.

You won’t really need to learn how to code as such - it’s just a case of picking up and using little (mainly CSS) snippets here and there to get your page doing what you want it to do. It’ll all just happen one step at a time and soon enough you’ll be sharing your learning with others here too.

1 Like

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