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

Mobile First Page: HTML, CSS(flexbox), Javascript, VSC, Brave browser

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

Solution retrospective


First of all, a big Thank You to Frontend mentor for providing this Challenge! Please feel free to dig into my code copy and share and provide the good, bad and ugly side, constructive criticism is always welcome. :)

Below Challenges and issues with some resolutions i found are..:

  1. Hamburger Menu: I know i could have used the image but i wanted some cool animation effects going on, so i used a Pure CSS approach using 3 span elements.

  2. Radio Buttons.: A: Styling them, I found challenging when styling them to put an outer border around them but managed to find a way round using the "outline" property in CSS, a solution provided from https://tinyurl.com/StyleRadioButtons3Ways . So all thanks to Joakim Lindberg for providing this.. 👍 and managed to show a nice animation when selecting the radio buttons. B: Using the "click "events from the EventListener gave a strange behaviour and got them working correctly using the ''change" events attaching the eventlistener to the radio button Id specifically, for example-: "radioBtn.addEventListener('change', showChanged);" where "showChanged" is a function i implemented that receives the events. This way i managed to get the radio buttons working ok.

  3. Page tearing for the Mask occurred when scrolling when the Modal/Dialogue cards were displayed when testing on my sgs8+ mobile. Here removing 'height:100vh' and putting in the full length in px resolved it initially.

Last but not least i have also added some nice animation to the progress bar loading which was much easier that expected.

Thanks again and looking forward to your feedback. Best regards,

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on GHNetCode's solution.

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.