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

Typemaster Pre-Launch Landing Page - Vanilla CSS

Lucas 👾•104,160
@correlucas
A solution to the Typemaster pre-launch landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


👾 Hello, Frontend Mentor community. This is my solution for the Typemaster Pre-Launch Landing Page

I finally finished all HTML/CSS only challenges (25/25). Now I feel ready to start to study Javascript and CSS frameworks. I had a really great time learning a lots about Vanilla CSS and html structure, flex and grid layouts.

A great challenge to sharp the Grid Layout skills and also work the layout around devices. The two aspects I spent more time was the hero section grid and the decorative pseudo-elements out of the container. Indeed to finish the pseudo-elements I had to ask help to my friend @AdrianoEscarabote that give me a lesson about the overflow property and parent/child elements.

If you can add something or give me some tip. I'll be happy to hear any feedback and advice!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,870
    @AdrianoEscarabote
    Posted over 2 years ago

    Congratulations Lucas for completing your personal challenge! It's really amazing how much you dedicate yourself to achieving your personal goals! It's really inspiring to have you as a friend!

    Everything is very good, the responsiveness of the project is incredible, and the details you added were very creative I think it went very well with the design of this page!

    Marked as helpful
  • MX•290
    @xingxing-prog
    Posted over 2 years ago

    Congratulations. It's not a simple challenge. All your project is so responsive and the layout is great.

  • Diogo•100
    @diogo-kappaun
    Posted over 2 years ago

    Cara, isso tá muito bom, gostei da estruturação do seu código, levarei como base para minha vida

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

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