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

Maker Landing Page

P
Øystein Håberg•13,260
@Islandstone89
A solution to the Maker pre-launch 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?

My biggest achievement in this challenge was using Grid and Subgrid for the pricing plan card layouts. I thought about using absolute positioning for the icons on the edge of the cards, but I think Grid is more robust, so I'm pleased with the result. Instead of using padding-inline on the card, I also used Grid and Subgrid to create 3 columns of the card, where columns 1 and 3 are set to the size of what the padding-inline would be, while column 2, where all the content is placed, takes up the remaining space.

I also tried to set up a 3-column grid on the body, again intending to have the content in the middle column, with columns 1 and 3 acting as potential "breakout" columns. However, after some experimentation, I used padding-inline instead.

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

The icon "boxes" in the middle was harder than I predicted. First I tried to set background-color on the images themselves, but I found out I needed to wrap them in a ````, for the background color and the padding. Since the icons are different widths and heights, I decided to give the icon boxes a fixed width, since they are all the same width and height in Figma. I centered the icons using display: grid and place-content: center.

As usual, I struggled quite a bit with the hero "decoration" - things such as background images, positioning, and transform are still top of my "least favorite things about CSS", haha. With some experimentation, I finally managed to get it right. I also managed to do the cool hover effect in the hero, by changing the stroke, fill and opacity on :hover.

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

As always, I'm open for any feedback :)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Øystein Håberg's 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 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.