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

blogr landing page with html css vanilla js

Dark-Lover•735
@Dark-Lover
A solution to the Blogr landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


hey guys ;) . after a break of 4 months, here I'm again. I'm waiting your feedbacks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roc Tanweer•2,500
    @RocTanweer
    Posted over 4 years ago

    hello @Dark-Lover, Great work on this challenge...!

    There is nothing for me to tell you after what @ApplePieGiraffe has told you...

    But one of the disadvantage is that your work is not matching the design file. Use Irfan View to measure the size of any part of an image (Like the design file provided from here).

    It will help you to develop the web site as close to the design as possible. You can now measure the button size or svg size or any part of any image.

    Jessica Chan(Coder Coder on YT) told me that...

    Hope it helps(Happy coding..!)

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hello there, Dark-Lover! 👋

    Welcome back (it certainly has been a while)! 😀 And nice job on this challenge! 👏

    Overall, your solution looks good and responds rather well! The only thing you might want to do is to open the dropdown menus in the mobile navigation menu when they are tapped, not hovered over (since users on mobile/tablet devices typically can't hover over elements). 😉

    Well, keep coding (and happy coding, too)! 😁

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

    Hello, great work you got there and welcome back I guess? :>>

    For the layout, it seems it is smaller than the original and the font-sizes needs to be adjusted as well, since right now, it might be hard for other user to see it properly since the components are far from their complementary element. Like the first section and first image, it will be good if the font-size is adjusted and the images as well.

    In terms of fluidity, your layout resizes well when going to mobile state.

    The dropdown in the mobile seems bigger to what it should be, therefore creating a huge white blank section if you drop on it.

    Considering those above will be awesome and overall, you did good here ^

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

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