Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

mobile first using Flexbox

P
Haydn Kerr•555
@haydnkerr
A solution to the Fylo dark theme landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Looking for resources to download the social media icons that are supposed to be in the footer section I couldn't find any decent ones that were compatible.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 4 years ago

    👋Hi Haydn Kerr! My name is Vanza!

    It seems like this project is not finished yet and also have a lot of issues. Try to fix those issues as soon as you can.

    For the icon you can download it from icomoon or you use font awesome.

    If you choose font awesome, you can put this link inside your head tag rather than create an account on font awesome.

    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css" integrity="sha512-iBBXm8fW90+nuLcSKlbmrPcLa0OT92xO1BIsZ+ywDWZCvqsWgccV3gFoRBv0z+8dLJgyAHIhR35VZc2oM/gI1w==" crossorigin="anonymous" referrerpolicy="no-referrer" />
    

    I have some feedback for this project:

    • You can use nav tag instead of div with the class of nav.
    • You can use section tag for each section rather than using a div.
    • The img tag must have alt attribute. But, you can leave it empty like this alt="".
    • Only use one h1 at a time since h1 is a call to action for every page.
    • Anchor tag also must have href attribute and you can't leave it empty like alt. But, you can do this instead href="#".
    • My recommendation to this project is that, try to do it slowly. There's no time limit so feel free to take as much time as you need.
    • Instead of use width: 90%, you can use padding-left and padding-right to prevent it touching the corner of the screen.
    • Use rem units instead of px, since rem will allow the use to change the font size based on their browser setting.

    I know it may be kinda overwhelming, but as the time goes on, you will get better. Just be patient!

    That's it! Hopefully this is helpful!

    Marked as helpful
  • Mojtaba Mosavi•3,740
    @MojtabaMosavi
    Posted almost 4 years ago

    I usually use font-awesome for icons but you can also make you're own icons.

    Keep coding :)

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