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

Portfolio

axios, react, styled-components, typescript, node
Oleksandr•690
@Oleksandr-Berd
A solution to the Minimalist portfolio website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Portfolio Website Challenge Welcome to my portfolio website project! In this project, I have built a multi-page portfolio website that showcases my projects and skills. This website is designed to be responsive, ensuring that it looks great on mobile, tablet, and desktop devices. I have utilized the provided designs to create a visually appealing and interactive portfolio.

Features Responsive Design: The website layout adjusts seamlessly to various screen sizes, providing an optimal viewing experience for users on different devices. Interactive Elements: Interactive elements throughout the site have hover states, enhancing user engagement and interactivity. Smooth Scroll: Clicking the "About Me" call-to-action on the homepage smoothly scrolls down to the next section, improving user experience. Contact Form Validation: The contact form validates user input and displays appropriate error messages if required fields are empty or if the email address is not formatted correctly. Technologies Used Frontend: React, TypeScript, Styled Components Backend: Node.js, Express.js Database: MongoDB Other Tools: React Router, Axios

Pages Homepage: Introduces me and provides a call-to-action to learn more about me. Portfolio: Displays a collection of my projects, categorized by difficulty level. Project Details: Offers detailed information about each project, including descriptions and links. Contact: Allows users to send me messages through a contact form. Usage Feel free to explore and interact with the website. Check out my projects, read about my skills, and send me a message through the contact form. If you're interested in my work, don't hesitate to reach out or use this portfolio as an inspiration for your own!

Acknowledgments I'd like to express my gratitude to the design team who provided the initial designs for this portfolio website challenge. Their designs helped shape the visual aesthetics and user experience of this project.

Thank you for visiting my portfolio website project. I hope you enjoy exploring my work as much as I enjoyed building it. If you have any questions or feedback, please feel free to contact me through the provided contact form. Happy browsing!

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