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

๐Ÿš€Blogr-landing-page | SASS | JS animations | Mobile-first workflow๐Ÿš€

animation, sass/scss
Samโ€ข1,190
@JustANipple
A solution to the Blogr landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone! i managed to complete this challenge!

My only concern is that the dropdown menu part has a lot of code to make it fit both the mobile and the desktop views, so it looks like there is something i'm missing

Is there any way to achieve the menu part with less code? do you recommend a framework like bootstrap to make this easier to tweak with?

Thank you all for the support!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chrisโ€ข520
    @9CB5
    Posted about 2 years ago

    Great work. It almost matches the design perfectly!

    As for your question, the code in your nav isn't that bad. There's naturally going to be a lot more code than a typical nav since this one has multiple dropdowns with lots of children inside. But you can really trim down your markup if you use a front-end framework like Vue for example and using list rendering with v-for for the dropdowns. You may also use tailwind to reduce code in your stylesheet.

    Going through your solution, I have noticed a few minor issues which I will highlight below:

    • The animation takes too long on the dropdowns and the fact that it starts off fast then slows down makes it feel clunky. You should aim to minimise waiting times for better UX.
    • The layout breaks on some screen widths. For example, when viewed on the iPad mini (768px), the header has a white gap on the right hand side, and on the surface duo (540px) some images are off-centered and there are some overlapping elements.
    Marked as helpful
  • Tola israelโ€ข100
    @tolabigboy
    Posted about 2 years ago

    Great work bro. Keep it upโ€ฆ You need to work on your site responsiveness. While shrinking your site page from desktop view to mobile view, I can see overflows in the page and also the buttons are not stable. This has more to do with your media query, I guess

    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

Oops! ๐Ÿ˜ฌ

You need to be logged in before you can do that.

Log in with GitHub