Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Single-page developer portfolio [HTML, Tailwind-CSS, React]

react, tailwind-css
Csaba Müller•260
@Csabooo
A solution to the Single-page developer portfolio challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi All,

This is my first "premium" project with react.js and Tailwind-CSS.

It was difficulter, what I thought first.

Br,

Csaba

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aman Singh Bhogal•1,010
    @asbhogal
    Posted almost 2 years ago

    Hi Csaba, great work! Developing a full page from a mockup is a significant step up, especially when using React and Tailwind together (which is often a common, maintainable approach.)

    Just a few things I've noticed which are worth considering when refactoring:

    • You have a horizontal overflow. I've debugged this using * { outline: 1px solid red } and found it's due to the background elliptical vector on the right hand side. If you change the position of this to relative, and adjust the values to the mockup, this will resolve the issue
    • Avoid using CRA for your builds. Meta no longer supports this. For client-side, front-end applications like this, use Vite, and deploy to a platform like Vercel instead of GitHub pages, as this is much more robust and designed to handle applications like these with better caching, performance etc.
    • Always locally host your Google Fonts for privacy and performance reasons.You'd need to download these fonts from Google, convert them to woff2 and upload them to your src files. Since you're using Tailwind, you can then reference them in your tailwind.config.js file (by either extending or overriding the default theme) Make sure to remove the @import directive in your index.css afterwards. Here's a good link which shows the first part (ie downloading and converting) Link and a link to Tailwind's documentation on how to then reference the files in your project Link

    Hope this helps!

    Marked as helpful
  • Csaba Müller•260
    @Csabooo
    Posted almost 2 years ago

    Hi Aman,

    Thank you very much for your comments and help. I appreciate it. I will have a look them and I take your advice. :)

    Br, Csaba

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

Oops! 😬

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

Log in with GitHub