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

Mobile first, BEM

Felix Criollo•575
@FelixCriollo
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • Use CSS without scss, it is more complicated.
  • how to make the nav better with js.

thanks for see my challenge.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, awesome job on this one. Layout in desktop looks good, responds fine and the mobile layout looks good as well.

    Some suggestions would be:

    • The alt for the website-logo img should have been alt="loopstudios", the image already has the text needed, better use it. Also when using alt attribute, avoid adding words that relates to "graphic" like "logo, image, icon..", img is already an image, no need to describe as one.
    • Do not use any other element inside ul element as a direct child unless it is li element. Only li element are used inside it as a direct child.
    • Do not remove the visual indicator for an interactive element outline if you removed this, make sure to add an indicator such as box-shadow or a custom outline on the :focus-visible state of the element.
    • The alt for the image after the hero-section needs to use alt="' since it is just decorative or maybe a meaningful alt kind of confused on this one.
    • see all needs to be a link a and not button, since it is supposed to be a link to a page to "see all" creations.
    • Each creation should have been a a tag because it serves as a link link for the specific creation the website made.
    • The hover effect on each card does not suits well, its light can hurt eyes and it makes the text not visible, adjust to another one.
    • Also, another one, always have a main element that will wrap the whole main content of the webpage. A preferred structure would be:
    <header />
    <main />
    <footer />
    

    FOOTER

    • Website-logo img should use alt="loopstudios".
    • The links below it should be inside nav element, since those are still your navigational links.
    • The social media links should be inside a ul element, since those are "list" of social media links.
    • Each a tag that wraps the social media should have been using aria-label attribute, to which the value corresponds to the social media it wraps. For example, the a tag that wraps the facebook should have aria-label="facebook", this way, users will know where this link would take them.
    • The svg for the social media should have been using aria-hidden="true" since it is just decor for the social media.

    MOBILE

    • Hamburger menu should have been using button element and not div. div alone is not accessible. Along with aria-expanded to which the value is changed by javascript, whether the user have toggled the button or not. Have a search for it the net.
    • The button that will be used in the dropdown should also have aria-label="navigation menu dropdown" attribute, this way users will know what this button does.

    Aside from those, great job on this one.

    Marked as helpful
  • nageeb0•5
    @nageeb0
    Posted almost 4 years ago

    very good

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