Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

GradientWave - A Stylish Landing Page

bootstrap, web-components, webflow, wordpress, styled-components
Moiz Azad•90
@Moiz3012
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


1- Design and Layout: What are your thoughts on the gradient design and color scheme used in this landing page? Does the layout and responsive design work well on various screen sizes? Any suggestions for improvement?

2- Content and Clarity: Is the content clear and engaging for visitors? Any suggestions for enhancing it? Do you think the title "GradientWave - A Stylish Landing Page" effectively represents the project?

3- Coding and Implementation: Are there any specific parts of the code that you find difficult to understand or improve upon? Are there any best practices or coding conventions that you think could be applied differently or more effectively?

4- User Experience: How does the landing page feel in terms of user experience and interactivity? Do you have any suggestions for making the user experience even better?

5- Overall Impression: What are your overall impressions of the project? Is there anything else you'd like to share regarding the project's strengths or areas for improvement?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • beowulf1958•1,890
    @beowulf1958
    Posted over 1 year ago

    Congratulations on finishing this project! I have a few suggestions. First, I could not get it to work on my computer; the Summary side overflows the card, and I can't see the svg icons (they are hidden by the overflow on the other side.) I found making the ".same" just a bit longer revealed the icons, and making the container <div> a bit bigger fixed the overflow problem.

    Next: the name of the project is very cool, but the style guide indicates ".card2" has a gradient background, and the button has an active state where it changes the background color to a gradient. Then it would be a GradientWave for sure.

    Last but not least, best practices on coding and implementation recommend to keep the CSS "DRY" (don't repeat yourself.) Declare the font family in ".card" and you can eliminate it everywhere else. Let the cascade do its job.

    Hope this helps! I look forward to seeing what you do next.

    Marked as helpful

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