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

Loopstudios Landing Page using Astro, Sass and CUBE CSS

accessibility, astro, cube-css, sass/scss
P
Kamran Kiani•2,780
@kaamiik
A solution to the Loopstudios landing page 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?

I'm most proud of how I integrated accessibility into the hamburger menu and achieved a responsive design across various components. Using Sass and CUBE CSS for styling allowed me to create a modular and maintainable codebase, especially as I built responsive grids in both the about and products sections. Next time, I’d like to experiment with a CSS framework like Tailwind to streamline some of the utility classes and explore more efficient ways to achieve responsive layouts.

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

One of the primary challenges was designing an accessible hamburger menu that worked smoothly across devices. I focused on making it accessible by implementing keyboard navigation and ensuring screen readers could interact with it easily. The responsive grid layout for the products section was also challenging, particularly in making it adapt well between mobile and desktop. For this, I utilized CSS Grid and media queries in combination to ensure it displayed optimally on different screen sizes.

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

I would like feedback on the HTML structure, especially regarding semantic use, and on the accessibility features I implemented. Additionally, any insights into optimizing CSS for responsive layouts or suggestions on how to further refine my Sass and CUBE CSS code for maintainability would be valuable.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elizabeth Shackelford•50
    @E-C-Shackelford
    Posted 7 months ago

    I want to acknowledge that I don't have experience with Astro, but as I explored your file structure and code, I found your organization to be clear. Separating concerns into folders like pages, layouts, components, styles, vendors, and subfolders and files improves your project's readability and maintainability.

    You have prioritized accessibility and user experience with keyboard-triggered focus states and ARIA attributes, and your consistent use of clear, descriptive variable and class names quickly communicates each class and variable's purpose.

    Your Product section's 'See All' button seems too small, which might affect some users' visibility and usability on mobile devices. I would experiment with different padding and font sizes–increasing these sizes could help mobile users tap the 'See All' button more easily.

    Perhaps add some comments to your code to ensure greater clarity, both for future developers and for yourself.

    Your file structure is solid, and your code is maintainable, accessible, and demonstrates strong attention to detail. You've done some great work in your solution to this challenge. I wish you the best of luck as you continue your coding journey!

    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