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

HTML5, CSS3, Vanilla Js, React, TypeScript

Artur da Silva Rezende•305
@ArturdaSilvaRezende
A solution to the Blogr landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first challenge here on the site, my only regret was not to have known Frontend Mentor before.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hey, great work on this one. The desktop layout I guess is fine, though the content are spaced out more. Though the mobile state is good and you made different approach on the pop up menu bar.

    Suggestions would be:

    • Please refrain from using vh as units especially on a container or an important component. Using vh will only limit your element based on the remaining viewport's height. So meaning, when a device have a smaller dimension, in terms of height, then the layout for them will change because your content is based on the viewport. Use another units like rem, those unit that will not scale with the viewport height. Try opening dev tools from the bottom, you will that your container, and the second phone image is scaling as well.

    • Your navbar link's font is not rendering the proper font. It is on the default, you might want to check that. Also, it will be better if a user clicks on another navbar link, while there is one dropdown that is show, making the former hides. Right now, I can select all of them and all of it shows, making the unclicked menu bars hidden will be really great.

    • White space. As you can see, there are large portions of white space on your 3 sections. It will better if you make the content more near to one another and not spaced out.

    • Multiple usage of h1. Though for some users, it is fine to use multiple h1 since there are no issue upon doing so right, but, for some users who uses screen reader, it might cause some issue. It is better to follow the right hierarchical usage of header tags. Starting from the h1 going down to h6, and not just all h1.

    • The mobile state for the dropdown, when I click on all of the three, they are now overflowing and the container does not respond to it very well, because there are declared height on it. It will be better if you remove those or much preferably, like what I stated above, make the former clicked dropdown be hidden, if a user clicks another.

    Also, clearing up those accessibility and html issues will be really awesome.

    But still, good job on this one^

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