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

Responsive Single-Page Design Portfolio with Grid and Flexbox

accessibility, lighthouse, progressive-enhancement, sass/scss, bem
Vanza Setia•27,715
@vanzasetia
A solution to the Single-page design portfolio challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone! 👋

A little bit of fun fact. When I started this challenge, I thought it was the single-page developer portfolio, not the designer. 😅

I am happy to be able to finish this challenge and learned a lot. I thought I would not be able to finish it because the slider was really hard to make—I still can make it by myself. Then, I decided to use a third-party library—which is a better way to say, "I borrow someone else's source code to create it". 😉

The most important thing that I learned was about using fluid CSS Grid. I am getting more comfortable to use RAM (repeat(auto-fit, minmax(..)).

Now for the questions:

  • What are the alternative texts for the images inside the "My Work" section? Right now, the alternative texts are "first work", "second work", and so on.
  • I tried the website on my mobile device in landscape orientation. I noticed that I could not scroll when I was on the slider section. My screen was full of the image and I could not scroll to the top or to the bottom. I got stuck. As a user, I could fix the problem by changing my device orientation to portrait. But, is that a problem?
  • The users always see a smooth transition on the slider even though they disable animations. I can not stop it with CSS. Also, I think a transition for the slide effect is essential. Without the transition, the slide effect will happen abruptly. What do you think? Should the transition on the slider get disabled?

Any suggestions for improvements are welcome. Also, you can ask me any questions about the technique that I used. 😁

If you have finished this challenge and would like me to give feedback on it, please include a link to your solution. I would be glad to help you!

Happy coding! 👍

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 Vanza Setia'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.