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

Responsive as fudge using HTML, CCS and JS. Flex makes an appearance

Gareth•410
@Gareth-Moore
A solution to the Blogr landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This one took me a lot of time to do and was the first really big project I did.

I'd like feedback regarding my JS code and particularly how I access the DOM.

All feedback is greatly appreciated and thanks for taking a look!

Gareth

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Karol Binkowski•1,620
    @GrzywN
    Posted almost 3 years ago

    Great job on the challenge!

    Your JS is decent, but you can make it more clean by assigning these weird looking i.children[0].children[1] for a variable and work on this variable instead of this thing. I recommend using more descriptive names for variables than just one letter (i in that case) e.g. element, item, service etc. Remember to use const instead of let, if you are not reassigning a value to a variable (almost always querySelectors). It makes your code more readable.

    There is also weird looking if/else statement. You can just negate it with ! mark.

    document.addEventListener('click', e => {
        if (e.target===servicesModal) {
        }
        else {
            hideModalLists();
        }
    })
    

    In this part of code you can just write

    document.addEventListener('click', e => {
        if (e.target!==servicesModal) {
        hideModalLists();
    }
    })
    

    Hope this helps! Have a nice day and keep coding!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub