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

Responsive for two devices using the tailwind component for header.

tailwind-css
satya surndra•180
@satya-hash
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feel free to provide your opinion about my code and your opinion is what I'm looking for. I found the most difficult part of this challenge is to make the landing page responsive. It took a lot of time to partially finish it. So I appreciate the feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Okafor Raphael•240
    @OkaforRaph
    Posted almost 3 years ago

    Hey @ Satya, Congratulations on completing the challenge 🎉.

    Here are some tips to help you on your next project..

    • First, there are issues with accesibility and HTML issues from your code which should be looked at.

    • Secondly, the arrow on your hero section is not there (From the preview).

    • Also, your code is not linked properly (I think you linked the wrong GitHub repository) so I can see your code to correct you further.

    Hope this helps, Happy Coding 😊

    Marked as helpful
  • prakhar•130
    @Prakhar-99
    Posted almost 3 years ago

    hello @satya-hash here some advise that I think make your sollution quite good 1 add background-repeat = no-repeat and background-position = center, background size = cover in all your background container. 2.when you apply media query change the flex direction of container that contain egg background image . 3 add margin from left, right in content (h1, paragraph and button) of class " left & right". and give some specific width to para of this classes. 4 give specific width to para of classes orange and cherry like 80%-85%.

    5.give a margin top and bottom in your testimonial section and give a width of 300 or 320px to your testimonia card and on flex wrap in testimonial card container thanks for read hope this can help you make your solution good

    Marked as helpful

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.

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