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

Minimalist Portfolio Website | VANILLA CSS, VANILLA JS & Hover Effects

accessibility, bem, bootstrap, sass/scss, vanilla-extract
Momin Riyadh•370
@momin-riyadh
A solution to the Minimalist portfolio website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I recently completed the frontend portfolio website challenge and wanted to share my thoughts and ask a few questions about the project. It was a valuable learning experience, but I encountered some difficulties.

One of the main challenges I faced while building the project was implementing a responsive design. Ensuring the website looked and functioned well across different devices and screen sizes were demanding. I struggled with positioning elements correctly and making them adapt gracefully to various viewport widths. Although I managed to make it work, I believe there is room for improvement in optimizing responsiveness.

Regarding my code, I'm a bit unsure about the performance optimization. While I focused on writing clean and readable code, I'm not confident I have implemented the most efficient algorithms or data structures. I wonder if there are any specific areas in my code that I should review for potential performance improvements.

Furthermore, I have some questions about best practices in frontend development. Firstly, what are some recommended techniques for improving website loading speed and optimizing asset delivery? I want to ensure that my portfolio website loads quickly and efficiently. Secondly, what are the current best practices for handling cross-browser compatibility? I want to ensure my website functions correctly across various browsers and versions.

In conclusion, the frontend portfolio website challenge was both rewarding and challenging. The primary difficulties I faced during the project were responsive design and integrating third-party libraries. Additionally, I have some concerns about code optimization and questions regarding best practices for performance and cross-browser compatibility. I appreciate any guidance or suggestions you can provide to improve my skills and enhance my portfolio website.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Momin Riyadh'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 1st-party linked stylesheets, and styles within <style> tags.

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.