Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
8
Comments
8
P

Vladyslav Novikov

@wtfkimiУкраина90 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • Meet landing page

    #react#webpack

    P
    Vladyslav Novikov•90
    Submitted about 2 months ago

    Grids


    0 comments
  • Testimonials-grid-section


    P
    Vladyslav Novikov•90
    Submitted 3 months ago

    grids


    1 comment
  • Four card


    P
    Vladyslav Novikov•90
    Submitted 4 months ago

    1 comment
  • Responsive parfume card


    P
    Vladyslav Novikov•90
    Submitted 4 months ago

    1 comment
  • Responsive Omlette page


    P
    Vladyslav Novikov•90
    Submitted 4 months ago

    1 comment
  • Social Link Profile


    P
    Vladyslav Novikov•90
    Submitted 4 months ago

    1 comment
View more solutions

Latest comments

  • P
    tasosbeast•150
    @tasosbeast
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?

    I'm most proud of the smooth animations I created using Framer Motion that enhance the user experience without overwhelming the interface. The staggered entrance animations, particularly in the Footer section, create a natural flow that guides users through the content. I'm also pleased with how I implemented responsive design, adapting the layout seamlessly from mobile to desktop while maintaining visual harmony across breakpoints.

    The typewriter effect in the hero section adds a dynamic element that draws attention to the key value proposition, and the step indicators with their growing vertical lines and pulsing effects create visual interest that helps users track their progress through the page.

    For next time, I would approach the animation planning more systematically from the beginning. While I'm happy with the final result, I ended up using a mix of animate and whileInView properties that could be more consistent. I would also implement a more structured animation system with reusable variants to maintain better code organization.

    Additionally, I would explore more performance optimizations, particularly for mobile devices. Some of the animations could be lighter weight for better performance on lower-end devices. I'd also consider implementing more interactive elements that respond to user actions beyond simple hover states to create an even more engaging experience.

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

    One of the most significant challenges I encountered was implementing the hero section's responsive image strategy. On mobile, I needed to display a single centered image, while on desktop, the design required two separate images positioned on either side of the content.

    I solved this by using the <picture> element combined with Framer Motion animations. This approach allowed me to seamlessly switch between the single tablet image and the split desktop layout without loading unnecessary resources:

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

    First, I'm looking for advice on the best approach for creating the hero image overflow effect. Currently, I'm using scaling techniques with scale-140 and negative translate classes to make the images appear to extend beyond the container

    Second, I'm concerned about potentially overusing animations. I've implemented various effects including:

    Fade-in and slide animations for content sections Parallax scrolling for hero images Growing vertical lines for step indicators Pulsing effects on numbered circles Staggered reveals for footer content Typewriter effect for hero heading Have I crossed the line into animation overload? I'm particularly interested in feedback on whether the parallax scrolling effect adds value or if it might be distracting to users. I'd also welcome input on which animations provide the most meaningful enhancement to the user experience versus those that could be simplified or removed to improve performance and focus.

    Responsive MeetLandingPage using React Tailwind CSS and Framer Motion

    #framer-motion#react#tailwind-css
    1
    P
    Vladyslav Novikov•90
    @wtfkimi
    Posted about 1 month ago

    Nice

  • Gabriel Schaal•120
    @Fayhild
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    I did it quicker than expected, a big improvement using background-url instead of html img elements. I added a media query to improve the design for devices from 800px to 1440px wide. I didn't focused on the font-size, so yeah, it could definitely be improved. I also could use flex-wrap instead of media queries maybe ? This proves to me that I don't really need CSS Grid for such a design if I'm comfortable with Flexbox.

    simple responsive solution using flexbox

    1
    P
    Vladyslav Novikov•90
    @wtfkimi
    Posted 3 months ago

    Have you even looked at the design??? Well, like, if you give such crap to the client, no one will pay you for the work, my advice is to look at the design and your work

  • Raivis•90
    @RaivisP
    Submitted 4 months ago

    Four-card-feature-section

    1
    P
    Vladyslav Novikov•90
    @wtfkimi
    Posted 4 months ago

    Everthing is good but mobile version not very nice, u should avoid hardcoding values ​​for width, check my preview card mob verison https://four-card-xi-dun.vercel.app/

  • macode09•10
    @macode09
    Submitted 4 months ago

    media queries, css

    1
    P
    Vladyslav Novikov•90
    @wtfkimi
    Posted 4 months ago

    Strive to make your layout minimally different from the layout, my advice is to learn to do it slowly but efficiently.

  • Bhagirathsinh8•10
    @Bhagirathsinh8
    Submitted 4 months ago

    Recipe Page using HTML and CSS

    1
    P
    Vladyslav Novikov•90
    @wtfkimi
    Posted 4 months ago

    The text color and font family do not match the design. The mobile layout does not correspond to the design. Additionally, the spacing is not consistent with the design. I recommend you look at the design and your solution and compare it. If I were the customer, I would not pay for such work.

  • hussainali99a•50
    @hussainali99a
    Submitted 4 months ago

    Social Profile with Responsiveness with CSS

    2
    P
    Vladyslav Novikov•90
    @wtfkimi
    Posted 4 months ago

    I recommend you look at the design and the design prototype and compare your solution with the design.

    Move the variables from Figma to a separate CSS file with variables, use flex and grid grids for layout.

    Look again carefully at the external and internal margins and compare with what you have. Or better yet, look at the code of my solution https://github.com/abidasfromearth/front-end/tree/main/Social-link-profile/public

View more comments
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

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

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