Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Built with NextJS, Tailwind CSS and Framer Motion

accessibility, next, tailwind-css, motion
solvman•1,650
@solvman
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud of figuring out how to do slide-down animation for a mobile layout hamburger menu.

What challenges did you encounter, and how did you overcome them?

Making this project fully tabbable was challenging. I overcame this challenge through research, trial, and error. It was interesting to figure out how to lock focus and make the drop-down hamburger menu fully tabbable.

What specific areas of your project would you like help with?

Any feedback is highly appreciated! I couldn't figure out how to make the transition between fonts on the mobile menu on hover smooth. Any suggestions on how to create a smoother font family transition animation are very welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    MikDra1•7,450
    @MikDra1
    Posted 11 months ago

    Creating a @font-face animation using CSS involves changing the font during an animation sequence. This can be done by defining multiple @font-face rules for different font styles or weights and then animating the font properties using @keyframes. Below is an example of how to achieve this.

    Define Your Fonts Using @font-face:

    • You need to define the fonts that you want to use in your animation. For example:
    @font-face {
        font-family: 'MyFont';
        src: url('path/to/font-regular.woff2') format('woff2'),
             url('path/to/font-regular.woff') format('woff');
        font-weight: normal;
    }
    
    @font-face {
        font-family: 'MyFont';
        src: url('path/to/font-bold.woff2') format('woff2'),
             url('path/to/font-bold.woff') format('woff');
        font-weight: bold;
    }
    

    Create Keyframes for Animation:

    • Define keyframes to change the font-weight (or any other font-related property) over time.
    @keyframes fontAnimation {
        0% {
            font-weight: normal;
        }
        50% {
            font-weight: bold;
        }
        100% {
            font-weight: normal;
        }
    }
    

    Apply the Animation to an Element:

    • Now, apply the animation to the desired element. You can set the duration, timing function, and other animation properties.
    .animated-text {
        font-family: 'MyFont', sans-serif;
        animation: fontAnimation 3s infinite;
    }
    

    Hope you will find this comment helpful 💗💗💗

    Good job and keep going 😁😊😉

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.

Oops! 😬

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

Log in with GitHub