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

Landing Page Project

Crystalis89•460
@Crystalis89
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 used a few things new to me this time:

Using lineargradient to darken an image or change opacity of a background-image without needing a separate overlay or messing with pseudoelements.

Using boxshadow to create the underline on hover without it changing layout from taking space like Border does.

Use clamp for the font so it can scale between screensizes smoother, particularly for the tablet middle size. Still do not 100% understand it but that more from lack of experience and poor math skills than confusion.

First time using Grid to create overlapping elements since I learned it a year ago, also as I mention below have trouble keeping them overlapping if screen to large (without using a breakpoint).

The "parent:hover child" selector pattern for the interactive button elements was a cleaner method than I used before.

Simplified the code for the sidebar nav from what I did prior projects slightly.

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

One big thing was that due to text not scaling well as shrink some window size, particularly the Hero, did not look right as size changed. To resolve that I had to learn how to use clamp() to set font size so it would more smoothly scale with window size keeping the box filled better.

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

Two problems that I keep having with all of the projects is that my scales are always a bit off, even if look perfect to me the screenshot after submission is not right.

I think the issue may be partly related to Chrome dev tools as things can look perfect in it for me at all sizes from 320px up to the 1440 target in style guide but when close devtools there will be at least a few things very wrong that don't look similar til zoom in 150% despite my screen not being big.

I would need to add another breakpoint to make it overlap correctly on my screen even if works perfectly 1440px and below

An area that keeps giving me issue is responsive layouts, usually from something shrinking changing the way it is positioned next to other elements.

In the case of this project the image for the "founding" blurb stays in same spot and resizes fine, but the text changes shape thus making it overlap less as the screen shrinks or move apart if grows to much even if I put in max values or 0 grow/shrink. And just the fact images react differently to changing size than text.

Having responsive elements maintain same shape and relative layout to surrounding elements is probably my weakest CSS skill right now that unlike everything else does not feel like I am improving much on no matter how much practice or read.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Marcello•480
    @marcello88c
    Posted 4 months ago

    Good 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 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