Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

News homepage --Responsive design using flex box and some javascript

Abdelrahman mohamed•230
@Tayara97
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

i still don't know how to use semantic HTML and if the nav should be inside the header or not

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

i am a beginner and it's my first project without tutorials so could anyone tell me if there is any problem with my code in CSS and what should I do instead

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nahin Moreira•240
    @nahinMSM
    Posted over 1 year ago

    Hello Abdelrahman Mohammed! All is well?

    The html isn't really semantic, but it's working, if you study a little more you'll get it quickly.

    In the css, if you remove the ("") the font will work.

    font-family: Inter;

    Marked as helpful
  • Nahin Moreira•240
    @nahinMSM
    Posted over 1 year ago

    Sure, here's a basic example of a semantic HTML structure:

    <!doctype html>
    • <html>
    • <head> <meta charset="utf-8" /> <title>My Page</title>
    • </head>
    • <body>
    • <header>
       <nav>
        <ul>
          <li><a href="#">Home</a></li>
           <li><a href="#">About</a></li>
           <li><a href="#">Contact</a></li>
         </ul>
       </nav>
       <h1>Welcome to My Website</h1>
      
      </header>
    • <main>
    •  <section>
        <h2>Introduction</h2>
        <p>This is the introduction to my website.</p>
      </section>
      <section>
        <h2>Main Content</h2>
        <p>This is the main content of my website.</p>
      </section>
      <aside>
        <h3>Sidebar</h3>
        <p>This is the sidebar of my website.</p>
      </aside>
      
      </main>
    • <footer>
    •   <p>Copyright © 2024 My Website</p>
      
    • </footer>
    • </body>
    • </html>

    These elements:

    <header>: represents the document header, which may contain a logo, a search form and/or a navigation menu.
    • <nav>: represents a section of the document that contains navigation links.
    • <main>: represents the main content of the document.
    • <section>: represents a generic section of the document.
    • <h1>, <h2>, <h3>: represent titles of different levels.
    • <aside>: represents a section of the document that is related to the surrounding content, but can be considered separate, like a sidebar.
    • <footer>: represents the footer of the document, which may contain copyright information, legal disclaimers and/or links to related documents.

    In "CSS" Semantic elements do not need "Class".

    Example: body { } head { } nav { }

    Focus on learning "Flexbox", it is very good for organizing the layout on desktop and mobile. On this site is a cool game to play: https://flexboxfroggy.com/

    Hope this helps.

    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

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