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

Agency-landing-page using css

Maysa-Tatour•120
@Maysa-Tatour
A solution to the Agency landing page 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 really proud of designing a complete website by myself. It was a challenging yet rewarding experience, and I feel a great sense of achievement. Next time, I would like to focus on making my websites more interactive and engaging for users.

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

One of the main challenges I encountered while designing the website was making sure it looked good and functioned properly on smaller screens. It was tricky to adjust the layout and ensure everything was responsive. To overcome this, I used responsive design techniques and tested the website on different devices to make sure it worked well across all screen sizes.

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

I would appreciate help with improving the interactivity of my website. I want to enhance user experience by adding more interactive features and ensuring the website responds smoothly to user actions. Additionally, I'd like assistance with optimizing the site for different devices to ensure it works flawlessly across all screen sizes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 5 months ago

    Hi @Maysa-Tatour,

    I've reviewed your solution and wanted to share some feedback:

    • If you faced challenges with smaller screens, I’d recommend adopting a mobile-first approach. This means developing for smaller screens first and then scaling up for larger ones. Currently, you're using @media (max-width: [number]px), which suggests you started with a desktop-first approach and then adjusted for smaller screens.
    • I noticed you're using <section> for various types of content. It would be better to differentiate elements by using more appropriate HTML tags. Many of these elements aren’t actual sections, so making this adjustment will improve the semantic structure of your page.
    • This challenge doesn’t require extensive interactivity, as there aren’t many buttons or call-to-action elements. However, you could enhance engagement by adding links to your social media accounts (Facebook, Instagram, X, Pinterest) at the bottom of the page, as the design seems to suggest their presence. Additionally, incorporating micro-interactions—like hover effects on <a> and <button> elements—would make the page feel more dynamic. You could also use CSS animations (animation property) to introduce subtle effects, such as sections appearing as the user scrolls.

    Hope this helps!

    Marked as helpful
  • Maysa-Tatour•120
    @Maysa-Tatour
    Posted 5 months ago

    Thank you for your valuable review and helpful feedback I will try applying the Mobile-First approach to improve the user experience on smaller screens. Regarding the use of <section>, I will review the HTML structure to ensure that the most appropriate elements are used for each part. Adding links and interactive effects is a great idea! I will work on enhancing the interaction with hover effects and CSS animations to make the design more dynamic.

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 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