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

Crowdfunding Product Page || React + TailwindCSS

framer-motion, react, tailwind-css
Boots 😺•1,610
@adityaphasu
A solution to the Crowdfunding product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Heyoo Everyone!

This was my first time using useContext() hook in a project to pass around props instead of doing prop drilling. I've only used one context to just try it out and didn't add another one (which I was thinking of doing for the modal but that would've just made it more complex for me to manage 😆)

Out of all the projects I've done using framer-motion this by far is probably the most fun one. It made me look more into other framer stuff like <LayoutGroup>, layout, and LayoutId and they did make the modal animations a lot smoother.

✨ I hope you guys give the website a go to test out the animations and lemme know how the experience is! and any feedback on how I can improve the code is much appreciated. (especially the usage of useContext hook and if I could've done it better)

Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ed•720
    @EdwinSch
    Posted almost 2 years ago

    hi Boots. Great solution! Looks very good, I also like your additions with framer motion. Just one thing which sticks out to me is de fact your header image doesn't scale and sticks left on desktop size. This can be solved with either implementating the image as a background-image for the container and let is scale with background-size: cover;. Or auto-fit it with object-fit properties.

    Coincidentally I was just planning on doing the same challenge, so I didn't check your codebase. Don't want to "cheat" by seeing someone else code beforehand. ;)

    Marked as helpful
  • Alex•1,310
    @AlexKolykhalov
    Posted almost 2 years ago

    Very good work!! Keep going!

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