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

A responsive landing page made with html, css and javscript

Zakariyah robiat•230
@zakariyahrobiat
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Comment on how I can improve my skill will be appreciated

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jeremy Tjahjana•140
    @JeremyTjahjana
    Posted almost 3 years ago

    Hi Zakariyah 👋, Congratulations at completing this challenge! I have a few things to say about your code:

    1. First off all center the whole thing by
    body {
        height: auto;
        display: flex;
        justify-content: center;
        align-items: center;
        font-family: 'Fraunces', serif;
    }
    
    
    1. Rather than doing
                <header>
                    <div class="logo">
                        <img src="img/logo.svg" alt="" srcset="">
                    </div>
                    <div class="navlink">
                        <a href="">About</a>
                        <a href="">Service</a>
                        <a href="">Projects</a>
                        <a href="">contact</a>
                    </div>
                </header>
    
    
    <-- Try this instead -->
    
    
    <header>
        <div class="logo"><img src="img/logo.svg" alt="logo"></div>
        <nav>
            <ul>
                <li><a class="nav-items" href="/">About</a></li>
                <li><a class="nav-items" href="/">Service</a></li>
                <li><a class="nav-items" href="/">Projects</a></li>
                <li><a class="nav-items btn" href="/">Contact</a></li>
            </ul>
        </nav>
    </header>
    

    Usually when creating things such as a navbar, using a list and an anchor tag is much more common then an anchor inside a div. Also usually a header/navbar is outside of the main section/container.

    3.There are too many classes

    <div class="first-container">
    <div class="second-container">
    
    <-- Both of these divs have the same purpose and yet it has different classes, 
    which means there is a lot more CSS you have to write, Such as:-->
    
        .first-container img,
        .first-container .text-container {
            width: 50%;
        }
    
        .second-container img,
        .second-container .text-container {
            width: 50%;
        }
    
    

    4.Why not just put the id on the image

        <div id="hamburger">
          <img src="img/icon-hamburger.svg" alt="" srcset="">
        </div>
    

    5, Play around with the dev tool, also the images are way too big as a result the web is overflowing in the X axis, maybe try to add a max width in the container or the image it self.

    6, Add transition effects to your hover state https://developer.mozilla.org/en-US/docs/Web/CSS/transition.

    7, There are a few more problems that i didn't mention because i myself don't know how to fix it. I recommend watching CSS tutorials. There are many great channels out there but i personally recommend Kevin Powell's Youtube Channel > https://www.youtube.com/kepowob.

    Some more advice:

    • Try to set a time limit for yourself
    • Try to make your code more reusable by adding certain classes and careful not adding too much
    • Try to reduce the amount of code, because 500 line of css is way too much
    • It's ok to copy paste things such as html cards, nav bar, or footer as long as you understand what they do and how to play with them

    I'm sorry that's all from me, correct me if i said something inaccurate :3

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