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

Loopstudios Landing Page with HTML, CSS and vanilla JS

Alizzie•140
@Alizzie
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi. It is my first time using grid and I learned a lot. I worked on it for five days in a row. Sometimes 2-4 hours, sometimes all day. I can't judge whether the duration is good or not, so I wanted to ask how long you usually are working for a challenge/ project.

Furthermore, do you know any good tools where you can measure the pixels of an image? I am currently guessing the width of the elements.

I will also be happy about some feedbacks. Thanks :D

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Devisetti Teja•530
    @Teja54
    Posted over 4 years ago

    This comment was deleted about 4 years ago

  • Chris•740
    @chrisbailey85
    Posted over 4 years ago

    Well done that looks great. On your social media icons the hover line doesn't go all the way across.

    I've never seen the figure tag before, after a quick Google I think I need to look into html a bit deeper, I would have ended up using div to make this.

    If you're on Windows you can open the files in the the windows photos right click and view file information and it will give you the dimensions.

  • Ameya Deokule•355
    @ameyadeokule
    Posted over 4 years ago

    Your work is really solid!! The only difference I could spot between the design and execution is that your header is a bit larger than the design other than that it is flawless IMO. Adobe Photoshop and GIMP provide a measuring tool that you can use, if you are using an Apple product their in-built photo viewer has this tool as well.

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.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub