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

FS Porfolio -> React - Styled Components - Node - Express - Nodemailer

node, react, vite, express
David•7,960
@DavidMorgade
A solution to the Single-page developer portfolio challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello and welcome to my Portfolio Solution

This was quite a great challenge to improve a bit more on my react knowledge and also start building some server side code on Node with Express to grab the form data and send it to my email directly from nodemailer

Extra Features

  • As I always do on my styled component apps, added light mode (still needs some improvement, thats why it will load as dark as default, but you can switch to light if you want to have a look!)
  • Of course themes gets save on reload (localstorage)
  • Added language switcher between EN and ES (using react context API and Json data)
  • Added a Nodemailer server as backend code here is the repo.
  • Added server side validation for all the fields with Express-validator
  • Added a custom domain https://www.developermorgade.es/

Built with:

  • React
  • Styled Components / Theming with Styled Components
  • Node / Express / Express-validator / Nodemailer

Working on:

  • Improve light mode and the profile image
  • Add more animations on scroll
  • Improve animations on the skill section
  • Add README to the Server repo

Feel free to try it at your own, send some request to the form also try tweaking the client side validation to see how the server side validation works!

At last if you want to use the node server for your own purpouse just add two step auth to your email and change the environment variables on your .env file.

Any feedback is welcome as always, I'm still trying to improve the Portfolio as much as I can, if you have any suggestion, please comment below!

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 David'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
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 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.