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

Response Social Links page

react, typescript, vite, tailwind-css
Nitin Srivastava•40
@nitindev3d
A solution to the Social links profile 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 learned how to setup a tailwind CSS project with react + vite + typescript.

Main challenge was to get started with the tailwind CSS that I tried for the first time.

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

Main challenge was to setup the project configuration in vite and tsconfig file for tailwind css.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Clark Tolosa•550
    @clakr
    Posted 5 months ago

    Hi! 🙋‍♂️ Congrats on completing the challenge.

    I suggest moving the variable buttons outside of the App component so it doesn't need to be recreated every time the App re-renders, maybe a bit irrelevant since the value isn't big of a data but I think it's a good practice to start a habit of saving processes when re-rendering ;)

    When iterating an element in React, it's best to have a key with a unique value attribute in the elements since this also saves processes of diffing the DOM tree when the App re-renders.

    I've been using Tailwind for a while now and I am curious what's your experience of using it in this project?

    If you have questions, concerns, feel free to bump me through this thread! 😁

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub