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

Crowdfund landing page

Kalp•220
@KalpChaudhary
A solution to the Crowdfunding product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Here's my site. I have done almost every task which was given . Except , mobile responsive. Sorry for that :\ but the rest of the stuff is just working excellent. Thanks :)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Darko•980
    @dtomicic
    Posted about 3 years ago

    Hey Kalp, I've looked at your solution and found some things you could improve.

    First of all when you're at the top of the page and click bookmark it refreshes the page, same thing with select the reward, when you click it it just refreshes the page and sometimes the back this project button doesen't open the modal until you scroll down. That sounds to me like a JavaScript issue and you should look into that.

    Next thing I stumbled upon is when the user donates the $ sign goes away from your total amount donated (image). Also when the donations go over a 100000 your progress bar goes out (picture), you can fix that by setting a max width on the progress bar fill so it doesen't go out even if the donations pass the 100000 mark. Next thing with donations is that you can input the negative numbers and then your donations go down (try donating -80000 and you'll see) you can fix that by just setting that the donation amount can't be less than zero.

    Mahogany reward should be grayed out and disabled while yours isn't.

    As for the modal you don't have any hover effects on the text and also a user can check all the boxes which I think shouldn't be possible (picture).

    Hope this helps you solve some of the problems and issues you have, you could also look into doing the mobile design properly (I would suggest for your future projects to do mobile-first design since it will be easier for you to scale it up later rather than having to scale it down).

    Other than that great job, keep it up 👍

    Marked as helpful
  • Duncan Kithinji•590
    @duncan91-ops
    Posted about 3 years ago

    Amazing work on the project. One point to note: (The number of rewards remaining(or left) should decrease by one after every pledge depending on the reward picked). Try it out and tell me what you think.

    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 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.