There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.
If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.
Join the Discussion. Help a fellow learner on their journey.
Ask or answer a question about this exercise by clicking reply () below!
Agree with a comment or answer? Like () to up-vote the contribution!
When you see the fonts listed, click the (+) button on the top right of the font you want. A pop-up appears in the bottom of your screen that says “1 family selected”. Under the “EMBED” section you can choose the link that is “Standard” or you can choose an “@IMPORT” link. This description follows the latest chrome browser. Using a different browser may be slightly different. Try using chrome if you are having troubles with following these instructions (Chrome is designed by google so fonts.google should work easily).
I also wasn’t sure about this, and in the examples given in this exercise, the first two include the type="text/css" attribute, whereas the third one doesn’t. So, I decided to investigate…
According to https://developer.mozilla.org/en-US/docs/Web/HTML/Element/link, when the linked document is a stylesheet (i.e. rel="stylesheet"), the type attribute can be omitted (and this is recommended), because apparently CSS is the only type of stylesheet language available on the web anyway.
This seems to imply that we can omit type="text/css"whenever we link to a stylesheet, not just when linking externally to fonts.
I remember seeing the answer to this in an earlier exercise’s forum discussion - I found it. The answer is that the type attribute can be omitted since html5.
Agree. The answer to this exercise seems to be out of date. And since it relies on an outside website as a source, the directions will give you an incorrect answer.
Correct, there is an issue with the current lesson, concerning “&display=swap”
This is a fantastic feature that we should all be excited for, but the lesson definitely needs to be updated to accept multiple responses, and potentially even add a quick lesson teaching what exactly display=swap does.
Still broken because of “&display=swap”
Report sent via Get Help > Bugs form, I encourage everyone to do the same (since these forums don’t seem to be monitored by Codecademy devs).
Still broken. BUT, I tried taking out &display=swap, then ran it again. It works! This may not be the perfect solution, but it might get you past this step.
) below.
) to up-vote the contribution!