Next JS - Tailwind

Community feedback

• 

  LINDECKER Charles•190

  @LINDECKER-Charles

  Posted 2 months ago

  Hi, 😊✨📝

  I clearly think React is way too heavy just for a single component. This article explains exactly what we should avoid doing: 👉 https://www.wired.com/story/internet-carbon-footprint/?utm_source=chatgpt.com 🌍💻⚠️

  ---

  README:

  In the blog-preview-card-main repo, you have a template you’re supposed to use for the README. Saying "This is a FrontEndMentor challenge solved by me. Live demo at..." is not a professional README. That’s just not acceptable if you want to present serious work. 📄❌🚫

  ---

  Website:

  Main issues:

  • The hover effect on “HTML & CSS foundations” is missing.
  • No drop shadow on the card.
  • Font sizes aren’t respected.
  • There are 3 errors in the console. If you really want to use React, do it cleanly.

  Optional issues:

  • Greg Hooper's profile picture is way too big.
  • Margins are not respected. 🧱📐🔧

  ---

  Code:

  • You shouldn’t name Tailwind custom colors randomly. customYellow is wrong. Use semantic names like primary, secondary, or even just yellow. 📚 https://mrtnschndlr.medium.com/things-to-rethink-with-tailwind-css-part-2-colors-6664c8079cfc 🎨🔤✅

  • Same with fonts: avoid names like MyCustomFont1, MyCustomFont2. Use clean, readable names. 📚 https://www.w3schools.com/css/css_font.asp 🖋️🔠📘

  • You skipped responsive design, assuming React handles everything. But even setting width={50} and height={50} would’ve helped. 📱📏🧩

  ---

  Conclusion:

  Unfortunately, this feels rushed. The README is almost empty, and the code isn’t clean. React can help save time, yes—but using it for a single static component just doesn’t make sense. ⏳🧼🛑

  00