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

Modern Profile Card Component with React & Tailwind CSS

next, react, tailwind-css
P
Dada Khalandar•255
@Syammed2429
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Modern Profile Card Component with React & Tailwind CSS

In this project, I leveraged the power of Next.js to create a dynamic and responsive Profile Card Component. Utilizing Tailwind CSS, I was able to style the component efficiently with a mobile-first approach. The combination of React's component-based architecture and Tailwind's utility-first CSS made the development process both smooth and intuitive.

Responsive Design: I aimed for a responsive design that adapts well to different screen sizes. Did you find any issues with the layout or design on various devices?

Code Structure: I used React functional components for this project. How do you find the organization of the code? Are there any improvements you would suggest for better readability or performance?

Tailwind CSS Usage: As a fan of Tailwind CSS for its utility-first approach, I'd love to know if there are ways I could optimize my usage of Tailwind classes.

Best Practices: Are there any best practices regarding React and Next.js that I might have missed or could implement better?

General Impressions: What is your overall impression of the application in terms of UI/UX?

Your feedback is invaluable to me, as it helps in refining my skills and understanding of front-end development. Thank you for taking the time to review my work!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,830
    @danielmrz-dev
    Posted over 1 year ago

    Hello, @kerrybli!

    Great job on this project! It looks really good!

    If you want to add that background pattern with the correct circles position, here's how you can do it:

    background-color: var(--Dark-cyan);
    background-image: url("./images/bg-pattern-top.svg"), url("./images/bg-pattern-bottom.svg");
    background-repeat: no-repeat, no-repeat;
    background-position: right 52vw bottom 35vh, left 48vw top 52vh;
    

    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