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

Fun exercise with Grid

P
Miran Legin•740
@miranlegin
A solution to the Single-page design portfolio challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi all,

this was a fun one!

Getting everyday practice with challenges like this really up your game a lot. I learned a bit like always but having some tough time with grid especially placing the Photography/Illustrations items on the grid like in design. Those of you who managed to complete this challenge will know what i'm talking about.

I really wanted to test myself in getting design without media queries but i finally decided to stop fighting and place some here and there. Probably could have done without it but switching text alignment is something i still need to learn without media queries. As far as i know this is not possible.

Anyhow looking forward to see your comments, probably the thing that i'm interested the most is markup for "Services" grid on the top of the page. Would it be possible to do it without extra markup for the middle column? I tried everything i can think of and was always one step away from the solution.

Also couldn't think of a better way to offset the image on the Tablet "breakpoint" so i used position:absolute to inherit height of the parent element and just align it to the right basically and let it overflow outside of the window.

Keep coding!

Cheers, Miran

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 Miran Legin'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.