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

mobile first site with bem and scss and javascript nav

Heritier Akilimali•310
@heritio
A solution to the Blogr landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Thanks for anyfeedback, If you have any recomendantions on how to abstract the nav javascript more, would be good for advice. And do you recommend to use different classes for javascript than css or just use the same, when selecting them.

Thanks for your time.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    j5•2,270
    @jmnyarega
    Posted about 4 years ago

    Hi @heritio, nice work on the challenge I have few suggestions.

    • If you are using BEM, you can not nest elements.
    • Prefer using relative units[ ems, rems] to pixels em-vs-rem-vs-px
    • It is advised not to use solid widths & heights, use max-width instead.
    • Feel free to use multiple media queries to adjust background images on different screen sizes.
    • Use max-width on text content to avoid text overstretching on big screen sizes.
    • Spacing between sections doesn't look proportional, You may want to use the same value.
    • You can use align-items: center, to place text content & images side by side.

    Otherwise, this was an impressive effort. 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

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