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

Crowfunding landing page with functional js, scss and BEM!!!!

Karim•590
@yasssuz
A solution to the Crowdfunding product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys!

This was a good one, the javascript part of the project to make everything interactive was hard, I need to admit! In the middle of the project, I switched from objected-oriented with classes to functional programming with pure functions. I clearly used the wrong programming pattern at the beginning, I'm not gonna use POO on something like this again.

I'm still testing everything to make sure that everything works properly and there are no issues or bugs. So if you guys found a bug, please make sure to report it!

But overall, I did a pretty good job with js. Probably I'm going to refactor a few things in the future but for now, I'm ok with the result.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Greetings, Karim! 👋

    Good job on this challenge! 👏 Your solution looks good, is responsive, and works rather well! 👍 I like how you styled the scroll bar in the modal that pops up! 😀

    I only suggest allowing users to select a backing option from modal by clicking on the entire option (or at least the heading of the option), not just the radio button itself (that'll make it easier for users to select an item). 🙂

    Oh, yeah, and adding a favicon to your site would be a nice touch! 😉

    Keep coding (and happy coding, too)! 😁

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 4 years ago

    Hey, great job on this one.

    In terms of layout, the desktop is good and the mobile state as well.

    Suggestion for the UI will be;

    • At mobile state, adding z-index on your menu-bg will be awesome so that it will overlap the bookmark button like it should do. Right now, when you click the menu bar, the bookmark button is still clickable and it should be hidden like that right. So adding that z-index will be awesome. Maybe like 10.

    • Adding a focus state on the different interactive elements will be really beneficial. Adding those supports more accessibility since a user will know where they are currently, especially when they are using keyboards. As of now, the sites lacks some of those, but the weird thing is the "out of stock" button have that focus state, which should not since it is disabled right.

    • I suggest not using height: 100vh on a main component or holder. You container selector is currently using that. So what happens is that it will only take the remaining size based on the viewport's height. So when you inspected it in dev tools at the bottom, it gets pushed on to the top and resizes it, which is not really ideal. Maybe using another units like rem will be awesome, so that it won't scale relative to the viewport.

    For the markup

    • I see that you are using a tags on those supposed buttons. So when everytime user clicks on it, it somehow redirects the user onto the same page since it is a link right. It will be better if you use .preventDefault methods on those element in your js. Or much preferably, use button elements.

    • Your modal as well is using a tags instead of buttons or having .preventDefault. So when a user, I, click on continue, it refreshes the website. Chaning some behaviors will be really awesome

    Overall, great job on this one^^

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

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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