Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Fylo dark theme landing page with html and css only

Ugorji Miracle•65
@amarealcoder
A solution to the Fylo dark theme landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback on my styles are welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Favourite Jome•1,110
    @jomefavourite
    Posted about 4 years ago

    Great job, I like the work and here are my feedbacks

    • Making use of the % unit to determine the overall width, using margin and padding of each section, without including max-width property will make the layout to keep growing on large screens.

    • Adding a max-width property to the texts on the page will be very helpful, so as to stop the texts from growing at a certain point.

    • The model with the selector .access, I noticed it isn't always centered so I made some changes.

    .access {
        padding: 5% 5%;
        box-shadow: 3px 3px hsl(0deg 0% 5%);
        height: auto;
        width: 80%;
        max-width: 700px;
        /* margin: -10% 21%; */
        background-color: hsl(217, 28%, 15%);
        position: absolute;
        margin-top: -110px;
        left: 50%;
        transform: translateX(-50%);
    }
    

    Also on the media query

    @media (min-width: 320px) and (max-width: 500px)
    .access {
        /* margin: -2% 5%; */
        padding: 1.5rem;
        width: 90%;
    }
    

    Lastly, I'll like to talk about the percentage unit you used frequently on margin and padding, it might cause issues as the viewport increases so I'll advise you make use of other responsive units like em, rem.

    Then on the width of each sections, you can use percentages. Well, it varies and depends on the use case.

    Here's an article I wrote that might be helpful.

    Also, I'll strongly advise you take this course Conquering Responsive Layouts by Kevin Powell.

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