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

Art Gallery Site

Naomi•30
@naomidzunic
A solution to the Art gallery website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Really happy with this challenge. I will say the biggest thing I'd need to learn is being able to create cleaner code when it comes to different-sized images (i.e. an image for desktop, another for tablet, and another for mobile). If anyone has tips on streamlining that that would be so helpful.

Also I know that it's important to add landmarks to the sections (i.e. <section</section>, <footer></footer>), however whenever I do I always have extra so I'm not sure if there's something I should be doing to be able to avoid that.

Anywho, any feedback is always welcomed!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Md5 dalton•1,430
    @md5dalton
    Posted almost 3 years ago

    Nice job Naomi...

    If you want to render alternative sizes of an image for different display or device scenarios, you can always use <picture></picture> element, it offers that functionality. If you want to read more on how to use it, here's a link to MDN web docs: The Picture element.

    I'll show you below an example of how you could have done it in your solution:

    <picture>
            <source srcset="assets/desktop/image-hero.jpg" media="(min-width: 1200px)" />
            <source srcset="assets/tablet/image-hero.jpg" media="(min-width: 751px)" />
            <img src="assets/mobile/image-hero.jpg" alt="hero"/>
    </picture>
    

    And there's no need for display: none on image selectors in your css.

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