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

LoopStudio

accessibility, bootstrap, sass/scss
CasperTheChild•420
@CasperTheChild
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?

:D

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

No challenges

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

he text in the photos also changes its opacity. I don't know how to stop it from changing.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    webdevbynight•530
    @webdevbynight
    Posted 3 months ago

    Some feedback:

    • your HTML code is invalid according to the markup validator;
    • you should better organise your projects, grouping your stylesheets into a folder;
    • when translating a design into code, the result should be as close to the original design as possible and your solution is not close to the design in some aspects:
      • the “See all” button does not match the button in the design (all sides should have a border),
      • each card does not have a transparency gradient when hovered,
      • the colour of the copyright text in the footer does not match the colour used by the design;
    • some classes should be refactored: for example, to declare that the whole menu uses the Alata font, you should just select the selector .nav__links (this would help you maintain your stylesheets in an easier way, avoiding useless repetitions);
    • you should learn more about semantics in HTML:
      • you put the header in a nav element, while such a header should be within a header element, the purpose of the nav element being to structure a navigation menu (and only a navigation menu, even if such a menu is within a header);
      • the logo should be within a h1 element, while the “Immersive experiences that deliver” text should be treated like a paragraph;
      • the “See all” button is, in fact, a link, and should be marked up as an a element instead of the button one;
      • each card should be treated like a link and, therefore, the p element could be replaced by an a element;
    • the image of each card should be inserted as an img element, not as a background image in CSS: even if these images are decorative, they can often be changed and using img in such a context should make maintenance easier (in other words, think of the people who will manage the contents of the website and will want to add, update or delete some creations and their images: they should be able to do that without having to know how to deal with your stylesheets);
    • concerning the problem you are facing and for which you ask for help, the problem is the use of opacity, which applies not only to the background, but also to the contents and the children of the element concerned (see MDN): therefore, a better way is to use a background colour with an alpha channel or a background with a gradient if there is a gradient (you can have a look at my solution to have an idea of that);
    • if you want to challenge yourself, try to use CSS without using a framework such as Bootstrap.

    I hope this feedback helps you.

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