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

Suite Landing Page VANILLA CSS (Custom Design + CSS Animations)

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

Solution retrospective


👾 Hello, Frontend Mentor coding community. This is my solution for the Suite Landing Page

I struggled a lot positioning the hero image and the heading decoration on this challenge, was really challenging place both elements between the mobile and tablet sizes. There's a lot of aspects to improve in my CSS writing, but I am happy with the result in this challenge.

🎨 I added some custom features:

  • 👨‍🔬 Custom UI Design + Logo.
  • 🧚‍♀️ CSS Animations

🍚Follow me in my journey to finish all HTML/CSS only challenges (Only 2 missing)! Gotta Catch ’Em All

Ill 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

  • Deborah Robbiano•600
    @debriks
    Posted over 2 years ago

    Another amazing solution!! Congrats ✨

    Marked as helpful
  • Pranshu Sahu•770
    @Pranshu-Sahu
    Posted over 2 years ago

    ** Hello, @correlucas, congratulation for completing the challenge. **

    Everything seems perfect ✨ and the solution is fully responsive. Its amazing to see your progress here.

    I have suggestion for you to remove your accessibility error:- In section.hero section you have used already <h1> for main heading, consider replacing <h3> , which you are using to display stats , by <h2>

    Since headings must be in a logical order.

    Hope this helps. 🎉

    Keep moving ahead. 🥇

    🏆 Best wishes with you , may you complete all HTML & CSS challenges

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

    Your solution looks perfect and it's really very responsive. Great.

  • Muqtadeer•340
    @hashmi7917
    Posted over 2 years ago

    nice work it gives me lot of inspiration

  • spacemanOG•120
    @SpacemanOG
    Posted over 2 years ago

    Your work is really amazing and I found inspiration from it! I recently started working on these challenges and I look forward to learning from you. Kudos!

  • Diogo Quina•30
    @DQuina
    Posted over 2 years ago

    Magnific :) Congrats

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

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