Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Galleria | NextJS | TypeScript | FramerMotion | Tailwind

framer-motion, next, tailwind-css, typescript
P
Aleks•330
@reactaleks
A solution to the Galleria slideshow site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Completing the challenge as close as possible to design. Overcoming issues i faced during this project. Learning new things like context and useRouter.

What challenges did you encounter, and how did you overcome them?

I needed to be able to control slideshow from different components. For this instead of using state and prop drill, i decided to use Context instead.

I needed to redirect user to relevant pages and have this reflected in url. For this i used useRouter.

I needed to figure out how to create a masonry layout for landing page. For this i used tailwinds: columns-4 utility class, however this created an issue where the masonry layout does not end with a straight line. This can be avoided by splitting the image items in to 4 grid columns with grid. However this solution did not suit me as it would mean i would have to create each column in the code and adding x amount of images to them. I prefer creating an array of gallery items with map.

What specific areas of your project would you like help with?

I was unable to figure out how to make the landing page gallery end with a straight line like on the design. I could create manually 4 grid columns and then create 4 image grid containers within, however this does not fit with my implementation of creating an array of components from data.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Aleks's solution.

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.