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

Responsive Loopstudios Landing Page with HTML, SCSS, JS and Vite

accessibility, sass/scss
Tharun Raj•1,330
@Code-Beaker
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?

This is one of my dream projects! ✨

I have wanted to complete this project this project from ever since I joined this platform. Today I finished it! It took around a week and half to finish and deploy the project. I didn't hurry and mess up my code. Instead did it patiently and effectively.

Built with: ⚒️

  • Semantic Vanilla HTML
  • SCSS
  • CSS
  • Vanilla JS
  • Vite

I initially started this project using Parcel. But I encountered an error of some of my elements disappearing on the live preview. After switching to Vite, I got them fixed.

I have tried my best to build an accessible and responsive website. Made use of aria properties for better accessibility and added interactive effects for users. As I mentioned, it took around a week because I was busy with school, else I think I could've finished it earlier. The layout itself is simple but the positioning of some elements is different from what I've built in the past. So, I am happy that I could break things down and build the best possible result.

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

I usually have a lot of difficulty building grid layouts and responsive navigation bars. But this time, I did things easily. Didn't google a lot. I did try using the new syntax for getting transparent background from custom properties.

.element {
background-color: hsla(from m.color(primary__black) h s l / .5);
}

I got this idea from Kevin Powell's last video and I found it really handy. I have always wanted an easy way to get a transparent background without having to copy-paste my hsl code and then converting it to hsla.

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

I would like to know how responsive it is on your devices. How to improve my JavaScript and build better and accessible websites.

Any suggestions on how I can improve are welcome! 😄

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    AnjelToppo•560
    @AnjelToppo
    Posted 13 days ago

    Well done!

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