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

Sunnyside agency landing page using Flexbox, CSS Grid and JavaScript

animation
Fazle Labib•400
@FazleLabib
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Would like to know what is the best way of creating the services section which consists of Graphic Design and Photography. I had a hard time positioning the text over the image to keep it consistent for different screen sizes.

Any other feedback regarding the whole design and suggestions on making the code more efficient is highly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kemystra•200
    @Kemystra
    Posted almost 2 years ago

    Another way you may consider is to ditch the use of padding for class service-content. Instead, set the property justify-content to flex-end. All of the text will then go to the bottom, and you can set the gap between them with the gap property (or just use margin, I guess). This guarantees your text to not overflow due to lack of empty vertical space.

    To do that however, you need to have a fixed height for the services-item class. One trick that I used is to set the aspect-ratio to be the same as the background-image's aspect ratio. For example, if the image is 400x500 in resolution, then I will do aspect-ratio: 4 / 5. This will maintain the div's proportion to the image.

    Marked as helpful
  • Ogunsanwo David Oluwadamilare•580
    @ogunsanwodavid
    Posted almost 2 years ago

    Alright, The best way to achieve this is to create a div (wrapper) with the respective images as backgrounds and then create another div inside containing all the texts and give it margin-top:auto so they can be always positioned at the far bottom. You should also give the wrapper or container a padding so the texts dont sit right on the bottom of the wrapper. I hope this helps.

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.

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