Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

Minimalist Portfolio Website (SASS + JavaScript)

sass/scss, accessibility
Malick Roungou•530
@mroungou
A solution to the Minimalist portfolio website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am very proud of the general layout of the project and how it turned out. There are a few areas where I could improve the layout to get it as close as the design which is something I would like to work on in the future. I am also quite happy about how I structured my code.

Next time I would like to start setting deadlines for when I should be completing my projects to simulate the real-world.

What challenges did you encounter, and how did you overcome them?

In an effort to practice my JavaScript I decided to dynamically change the content displayed for the projects. I couldn't figure out how to register which project was clicked on the portfolio website and load the projects page and display the selected project.

I was able to use session storage to store the index of that project when clicked.

What specific areas of your project would you like help with?

Here are the areas I need help with:

  1. I would like to add animations for the closing and opening of the menu on mobile
  2. add animations when I dynamically add content to the DOM when the user is going through the different projects
  3. when the page is initially loaded, the home link isn't highlighted and when you open to the portfolio page and you click one of the projects, all the links are being highlighted instead of just the portfolio link.

All suggestions are welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Malick Roungou'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.