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

Fylo dark theme landing page (React JS + Tailwind CSS + Framer Motion)

accessibility, motion, lighthouse, react, tailwind-css
Melvin Aguilar 🧑🏻‍💻•61,020
@MelvinAguilar
A solution to the Fylo dark theme landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there 👋, I’m Melvin and this is my solution for this challenge. 🚀

🎁 Features:

  • Little animation with Framer motion using useReducedMotion hook. 🎬
  • 97%/100% on lighthouse report and PageSpeed Insights. 🚀
  • Tested with the TalkBack screen reader on mobile. 📱
  • Custom scrollbar. 🖱️

🛠️ Built With:

  • React JS. ⚛️
  • React Hook Form. 📝
  • Framer Motion. 🎬
  • TailwindCSS. 🎨
  • npm - prettier - prettier-plugin-tailwindcss. 📦

Any suggestions on how I can improve and reduce unnecessary code are welcome!

Thank you. 😊✌️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Arseniy AI•170
    @ArseniyX
    Posted over 2 years ago

    Hello, its looks awesome! Design looks incredible so I don't have any suggestions

    Code improvements:

    1. You have hardcoded static data inside HeroSection.jsx and other components
    2. You have code comment in Illustration.jsx that need to be removed
    3. in utils you have file name motion.js its just animation utils not necessarily for motion so it need be renamed
    4. instead of doing {/* prettier-ignore */} you can make svg as component in this case you can put it like independent file .svg in assets
    Marked as helpful
  • Aruj Joshi•290
    @gtalin
    Posted over 2 years ago

    This is beautiful. You have matched the design perfectly.

    The subtle animations you have used are are just right. This must have taken hours of diligent work.

    Love the input field validation and how on typing a valid email the error message disappears.

    I have one small question/suggestion. Right now when the user submits the form, an error message is displayed. The error message then does not disappear when the user abandons the form and focuses away from the input field. Maybe the error message can be removed when a user focuses away from the input field. This is just a suggestion. And you might have consciously designed it that way.

    Marked as helpful
  • Kehinde•680
    @jonathan401
    Posted over 2 years ago

    Wonderful solution as always 🎉🎉. Just curious though, how do you match the design exactly. It's always eluded me 😅. I'll like to make my solution match the design but since I'm a free subscriber, it's really hard achieving that 😅. Any tips on how I could match the mobile and desktop design 'perfectly'?

  • Arman karimi•80
    @iArmanKarimi
    Posted almost 2 years ago

    Great job on your solution. The design looks fantastic, and you've done an excellent job recreating it. The animations using Framer Motion add a nice touch, and your use of React JS, Tailwind CSS, and React Hook Form is impressive. It's also worth mentioning that your attention to performance optimization is commendable, as reflected in your high scores on the lighthouse report and PageSpeed Insights. Overall, your work is highly professional and visually appealing. Keep up the good work.

  • cjrdelosreyes•40
    @cjroma0199
    Posted about 2 years ago

    This is just fantastic, and it's pixel-perfect. I'm really loving it. It's inspiring me to work hard and reach this level of skill and talent too :).

  • Dylan Guaquier•340
    @dylanguaquier
    Posted about 2 years ago

    Wow, that's impressive, congratulations

  • Nature Son•1,100
    @NatureSon22
    Posted about 2 years ago

    Wow, your works never fail to amaze me! I hope I can also be as good as you someday <3

  • Pouria Zamehran•260
    @pouripz
    Posted about 2 years ago

    How many days did it take you to make this? it is so beautiful 🤩

  • Lucas 👾•104,160
    @correlucas
    Posted over 2 years ago

    Keep going bro! You gotta won this year. 😎

  • Bilal Türkmen•340
    @bilalturkmen
    Posted over 2 years ago

    nice and meticulous work.

    Custom scrollbar is a nice detail. I liked framer motion, want to try too 🙂

  • marko-zivanic•60
    @marko-zivanic
    Posted over 1 year ago

    you're amazing, do you have a personal website?

  • AbdulakhaD 💻•70
    @AbdulahadIKramov
    Posted almost 2 years ago

    Very cool you have completed the given assignments 1 = 1 How did you achieve this

  • Nelson Guiamba•140
    @NelsonGuiamba
    Posted about 2 years ago

    Amazing job, how did you make it so pixel perfect I have some problems with font sizes and widths

  • SURU EMMANUEL•390
    @suruaino
    Posted about 2 years ago

    Hello, I have no correction rather than a question. To me as an up-coming, you have done it perfectly well to match the given design.

    my question is; how did you manage to match it so well and almost perfectly?

  • Syed Bilal•260
    @syed-bilal205
    Posted over 2 years ago

    Your Work is fantastic from where did you all learn this any youtube channel for recommendations am also doing projects.....

  • Gerardo Roloff•20
    @groloff
    Posted over 2 years ago

    great job on this. very precise, to pixel perfection level one question: did you use React for any particular reason? I mean, what´s the advantage of using React instead of simple HTML, CSS and JS for this project?

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

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

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

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

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

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

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

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

Oops! 😬

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

Log in with GitHub