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

Responsive landing page with graph animation using React & Framer

gatsby, react, motion
ThaBeanBoy•230
@ThaBeanBoy
A solution to the Expenses chart component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was a really good start with Gatsby Js, I learned the basics. I was disappointed with the fact that I didn't work a lot with images. Gatsby has a few plugins that optimise images, & I really wanted to experience that. The only image I had to work with was the logo image, but the plugins don't support SVG images. I just put the logo image in the static directory.

What I enjoyed most about Gatsby is the fact that it's an SSG (Static Site Generator). This really boosts SEO performance compared to React projects. This happens because React performs client-side rendering.

During development, I went through one of the most traumatic events in my web development career, NPM Peer dependencies. I learned that modules can depend on each other, but due to different versions, this can result in peer dependency errors. Never in my life have I appreciated Git & GitHub. Although I didn't resolve the issues, (I just moved back to the previous commit), this really exposed me to some of the inner workings of NPM.

Live Site - https://frontendmentorexpenseschartcom.gatsbyjs.io/

Hosting - https://www.gatsbyjs.com/products/cloud/

Repo - https://github.com/ThaBeanBoy/Front-End-Mentor-Expenses-Chart-Component

Front End Mentor - https://www.frontendmentor.io/home

Challenge - https://www.frontendmentor.io/challenges/expenses-chart-component-e7yJBUdjwt/hub/expenses-chart-component-pRP0otU6Pw

Framer Motion - https://www.framer.com/motion/

My Github Account - https://github.com/ThaBeanBoy

Linkedin - https://www.linkedin.com/in/gibbs-chipoyera-0948b9193/

Instagram - https://www.instagram.com/tiin_giib_chiip/

#googlefonts #webdeveloper - #webdevelopment - #webdev #webdesign

  • #uidesign
  • #design - #ui #figma
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on ThaBeanBoy'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 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.