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

Responsive landing page with graph animation using React & Tailwind

gatsby, react, tailwind-css
ThaBeanBoy•230
@ThaBeanBoy
A solution to the Fylo landing page with two column layout challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is the first time I ever touched Tailwind CSS. The thing I love about it is that I still had control over how I styled my components through utility. Something that I really enjoyed is that I didn't have to constantly jump between JSX & CSS files. This made it feel like I was saving a bit of time during development.

I love how you can configure Tailwind. In this project, colours & fonts were given, which were easily included in the config file. One thing I had to get used to was putting all the breakpoints in the config file.

I was worried about how everything would look if I used tailwind, but while reading through the docs (https://tailwindcss.com/docs/utility-first), my worries were alleviated. Something I also really loved was Automatic class sorting with Prettier.

The last thing I had to adjust to, was learning how to develop in a mobile-first development workflow. It didn't really take time to adjust, especially considering how you can make websites responsive using Tailwind.

Although the current config file has different screens, colours & font-families, what was lacking was proper spacing & font sizes. This could probably be attributed to the fact that I didn't have access to the actual design file, but rather the images of the designs alone. So I had to approximate the sizes. Using opening the design images in Figma helped when trying to determine things, but it's not always accurate.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,890
    @AdrianoEscarabote
    Posted over 2 years ago

    Hi ThaBeanBoy, how are you? I really liked the result of your project, but I have some tips that I think you will enjoy:

    The links must have an aria-label or sr-only text that tells where the link navigates the user. For example: Visit our Facebook. For images, you should set aria-hidden=” true” to be ignored by screen readers and to avoid redundancy and repetition.

    <html> element must have a lang attribute [click here](https://dequeuniversity.com/rules/axe/4.3/html-has-lang?application=axeAPI)

    I noticed that this image is appearing in higher resolutions, you probably didn't notice ahuahuahu

    <img data-main-image="" style="opacity: 1;" sizes="(min-width: 375px) 375px, 100vw" decoding="async" loading="lazy" alt="curved background" src="/static/5f0b90e83abae7337bca43e2ee067cbe/c2ffb/bg-curve-mobile.svg" srcset="/static/5f0b90e83abae7337bca43e2ee067cbe/d3757/bg-curve-mobile.svg 94w,/static/5f0b90e83abae7337bca43e2ee067cbe/9b482/bg-curve-mobile.svg 188w,/static/5f0b90e83abae7337bca43e2ee067cbe/c2ffb/bg-curve-mobile.svg 375w">

    The rest is great!

    I hope it helps...

    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

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.

Oops! 😬

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

Log in with GitHub