Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

HTML SCSS VANILLA JS

sass/scss
Alucard•870
@Alucard2169
A solution to the Crowdfunding product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Still have some bugs, working on them.

Hope you like it. feedback would be appreciated.

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Christopher Adolphe•620
    @christopher-adolphe
    Posted about 3 years ago

    Hi @Alucard2169,

    You have done a good job overall. 👍 Here are a few things that I have noticed and you might want to check in order to improve your solution.

    HTML:

    • The <div> elements for main-card, stats-card and about-card could be replaced by <section> elements for better semantic.
    • A <progress> tag already exists in HTML. You could have used that instead of styling it with a <div>. It will make thing easier to manage when the progress is dynamic. Read more here
    • You really don't need a separate main navigation for mobile. You can use the same markup and adjust the styles using media queries.
    • The modals are missing a backdrop. This will prevent users from interacting with other elements of the page because at the moment users can see both the Thanks for your support! and Back this project. You could refactor the html code for the modal like this:
    <div class="modal">
      <div class="modal__container">
        <div class="modal__content">
          <div class="modal__header">
          </div>
    
          <div class="modal__body">
          </div>
    
          <div class="modal__footer">
          </div>
        </div>
      </div>
    </div>
    
    .modal {
      position: fixed;
      top: 0;
      left: 0;
      display: flex;
      justify-content: center;
      align-items: center;
      width: 100%;
      height: 100vh;
      overflow-x: hidden;
      overflow-y: auto;
      background-color: rgba(0, 0, 0, 0.15);
      z-index: 1000;
    }
    

    SCSS:

    • Since you are using Sass, try to move the styles for different components in dedicated files (a.k.a partials) and then import them in your styles.scss file. This will help keep your stylesheet more readable and maintainable in the long run.
    • Keep an eye on the level of nesting of your css selectors. Deeply nested selectors lead to overly specific and less reusable rules which are too reliant on the HTML structure. At the moment, most of your selectors are dependent on the <main> element. Try to keep the nesting to a maximum of 3 levels deep.

    JS:

    • Maybe you should consider to reset the form in the Back this project modal after the user has entered a pledge amount and has clicked on Continue.

    Hope this helps.

    Keep it up.

    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