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

Responsive portfolio website in React/Typescript

react, tailwind-css, typescript, react-router
Hervé•80
@HerveDelaunay
A solution to the Minimalist portfolio website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey everyone, happy to submit my solution to this challenge,

First of all I've got an issue in my code : the "about me" button of the homepage is not behaving like it should be on mobile version. The background color of the button should turn white after clicking, and turn back to blue after losing the focus. Weird thing is that everything is working perfectly in my chrome inspector (on the mobile breakpoint) but not on my phone. In any case I would like to know if anyone of you have a better solution concerning the switching of the button color on the hover, especially for the arrows which are in SVG format.

If you go to the component "ProjectDetails" in my code you'll notice that I'm making a lot of import, and I would like to know if there is a solution to make all of these imports in a separated file.

Concerning the responsive part of the project, I'm puting fixed size for the different elements of my pages, and these fixed sized switches to other fixed sizes after passing a breakpoint. As they are fixed sizes they are not adapting to the screensize while being inside the same breakpoint. Should I put % instead of fixed width or is it correct to put fixed sizes ?

I'm planing on adding a feature on the form. After submitting the form, the user's mail application will open will all the data automatically field, or a gmail new tab will open in the same fashion. Have any clue how to do it (without package if possible)

For the rest I'm interested in any advices that you could give me reviewing my code, I know that there is a lot to improve.

Thanks in advance !

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Hervé's solution.

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.