Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

i managed to do this challenge just using basic concepts of css,html

cube-css, backbone
Alejandro Cañon•260
@alecanonm
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Just because im a beginner i didn't know where to start that was the most difficult part, and there are somethings that i dont understand yet, for example about add fonts from google or use the apis from google, maybe that's get me freaking out

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jeanco Volfe•460
    @engsofjvolfe
    Posted over 2 years ago

    Hey bro, keep practcing... Heres a thing that u can do to change the fonts:

    To use Google Fonts on your HTML CSS web page, follow these steps:

    Browse to the Google Fonts website at fonts.google.com and select the font(s) you want to use.

    After selecting a font, click on the "Select This Font" button, and then click on the "Embed" tab.

    Copy the code provided under the "@import" or "link" tab. Paste the copied code "link" into the head section of your HTML file. The "@import" you paste on first line of your "principal" css, but choose just "link" or "@import" to use ok?

    Next, add the font family to the CSS styles for the element(s) you want to use it on. For example, if you want to use the "Open Sans" font on all paragraphs on your page, you can add the following CSS:

    css

    p {
      font-family: 'Open Sans', sans-serif;
    }
    

    Note that the font name in the CSS must match the font name in the Google Fonts code.

    Save your HTML and CSS files and view your webpage to see the changes.

    That's it! Your webpage should now be using the Google Font you selected.

    Marked as helpful
  • Melvin Aguilar 🧑🏻‍💻•61,020
    @MelvinAguilar
    Posted over 2 years ago

    Hello there 👋. Good job on completing the challenge !

    I have one suggestion about your code that might interest you.

    • Use "./" before the file path of the styles to display it.

    ‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎✅ Do: <link rel="stylesheet" href="./styles.css" />.

    ‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎❌ Don't: <link rel="stylesheet" href="/styles.css" />.

    More information.

    I hope you find it useful! 😄

    Happy coding!

    Marked as helpful
  • Mr Rabbit•1,020
    @rabbitmaid
    Posted over 2 years ago

    Keep up the good work till you're done

    Here is a little tip! Hope it helps

    • HTML5 elements such as <main>, <nav>, <header>, <footer>, <section>, <aside> act as landmarks, or special regions on the page to which screen readers and other assistive technologies can jump. By using landmark elements, you can dramatically improve the navigation experience on your site for users of assistive technology (Users with disabilities) .

    You can use the <div> for sub items within landmarks like <section>. In other words for containers or sections in your HTML you can use the <section> tag if you want to nest in sub items <div>.

    Landmarks such as the <section> may actually require that you specify a heading within. In other words if the section has no heading it may throw an error when checked by an accessibility tool.

    It is advisable that you place all your main site content in a landmark element <main> Here is an Accessibility Evaluation Tool to check your webpage for any errors or warnings related to landmarks.

    There exist an attribution <div> that comes with the frontendmentor starter kit. You will have to wrap this <div> in a <footer> tag

    Read

    • W3schools Accessibility Landmarks Notes for more information.

    • MDN Web docs notes for more information.

    I hope you find the above solution useful! 😄 Nevertheless, the solution you submitted is great! Happy coding!

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub