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

Galleria Slideshow using Astro, Sass, Tailwind and Vanilla JS

accessibility, astro, cube-css, sass/scss, tailwind-css
P
Kamran Kiani•2,780
@kaamiik
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?

This was one of the projects that might serve as a foundation for similar work in the future, possibly in a professional setting. It was incredibly helpful for my learning. While it wasn’t particularly challenging in terms of technical complexity, I gained a lot of valuable experience.

The project includes numerous pages, each featuring an article about a specific painting. I used dynamic routes in Astro to create these pages. The main page features a Masonry Layout, and I gave it my best effort to implement it, though I’m not entirely sure it was the optimal solution.

In the future, I plan to revisit this project and rebuild it using a framework to create it as a single-page application (SPA).

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

The main challenges were related to CSS, particularly in creating the Masonry Layout and designing the painting pages to use Grids effectively across different screen sizes.

Additionally, I experimented with dynamic routes in Astro to build multiple pages, which was my first time working with this technique.

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

I used Astro to build this project, including dynamic routes. I’d like to know if my approach is correct for creating multiple pages within a folder. Specifically, I added a [slug].astro file and used a data.json file to generate the pages.

Regarding the CSS, is my implementation of the masonry layout correct?

If you notice any other issues in my HTML, Accessibility, or CSS, I would appreciate your feedback on those as well.

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 Kamran Kiani'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 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.