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

Galleria slideshow site

react, vite, react-router
Roan Macmillan•820
@RoanMacmillan
A solution to the Galleria slideshow site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello! 👋

This ended up being a lot tougher than I expected, for a few reasons.

  • Because I pulled the data from the json file it kinda added an extra layer of complexity for me as I'm still getting to grips with React, and made styling the masonry layout a bit more confusing.

  • The masonry layout was pretty tough, decided to try and use grid as I'm inexperienced with it and need the practice. Originally tried to use a masonry library but it seemed a little buggy so didn't bother with it. Not sure what the best approach would be.

Overall happy enough with what I came up with, but feel like my code and react components could have been way more structured. Any feedback is welcome! 🙂

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Allison Alencar Ribeiro•80
    @ribeiroAllison
    Posted about 2 years ago

    Hey Roan, congrats on finishing this project. It looks really nice!

    Really liked the transition effect you designed, much better than hard cuts between pages. The name being hidden until hover was a nice touch too!

    Also, the progression bar looks cool. I sure couldn't pull that off in my solution :) .

    One thing I didn't quite get was the huge black bars around the page on bigger monitors. Was it a deliberate choice so you didn't distort the art on the detail page?

    As for the slideshow, I supposed it had to roll out all the art pages automatically, at least that is how I designed it.

    Anyway, nice work! I'll be sure to check your code on how to make these beautiful transitions.

    Cheers, Allison

    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
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