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

Blogr landing

Adam•430
@aemann2
A solution to the Blogr landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The mobile version looks pretty spot on. The desktop is...kinda yikes. Once it came to styling the desktop, I felt like every decision I made when setting up the HTML for mobile-first came back to haunt me, and every style on desktop was a big headache.

Is there a strategy to setting up your HTML so it adapts well when scaled up to desktop, so you don't have to go back and add a bunch of wrapper divs and CSS overstyling? Or do you just have to look at the desktop sketch and try to anticipate all your layout shifts when you're setting up your HTML for mobile?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chamu•13,820
    @ChamuMutezva
    Posted almost 4 years ago
    • since this <div class="navbar__hamburger" id="hamburger"></div> is supposed to be interactive (button) , users of assistive technology will not be able to identify it as such, hence they won't be able to utilise it
    • the immediate child of a ul element should be an li element. A div can only come in as a child of the li element.
    • your list items Overview, marketplace, features etc should be anchor tags since generally they should be links to other pages
    • as to your question about the strategy of setting up html: i think they are somethings that cannot be avoidable until you have mastered the ins and outs of the game. The planning must be done with both or all the designs in mind but that can change during implementation resulting in the addition and or subtraction of the ideas.
  • P
    Patrick•14,265
    @palgramming
    Posted almost 4 years ago

    Maybe someone else can help you with you SASS but it seems like you are holding the mobile navigation too long a the browser window widens

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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