Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

React.js + TypeScript + Firebase + SCSS Testimonials Grid Section

bem, react, sass/scss, typescript, animation
Better5afe•850
@better5afe
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Summary:

  • Upon entering the page, users will see a loading animation while the data is being fetched from Firebase. To make this feature more prominent, the fetching function is embedded inside a setTimeout() function which delays it - I would not do this in a professional app tho.
  • If the data fails to be loaded, the users will see a simple error message.
  • If the data is successfully loaded, the users will see different animations and layout depending on their device's screen size.
  • Desktop layout is based on CSS Grid.

Feel free to leave any feedback.

Thanks & Happy Coding! 🎃

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • solitary_coder•1,000
    @kabir-afk
    Posted over 1 year ago

    Hey!!, nice page , altho I'd recommend that if you are already using these technologies then you should try leveling up in your animations as well . . . .I noticed that you were using @keyframes in your page for animations , not that they don't look appealing, they're great , but they don't provide you with much diversity . . . since you are already using react , don't you think that Framer is a better choice ? If you prefer not to use Framer Motion, you can also explore GSAP. It has a really similar syntax to @keyframes. I highly recommend giving it a try in your upcoming projects . . .hope you find it helpful . . . and as always , keep the grind 💪💪

    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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub