Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

News homepage using HTML, CSS & JS and layers

pure-css
Enes Aliev•330
@Enes-hacker
A solution to the News homepage 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 proud that I have experienced new featureslike adding layers in css. I have learned bunch of new things from this tutorials. It tooks much time to complete it but I did it eventually

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

The entire project was a challenge for me

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

The design looks great but when I have hosted vith github pages itsome of the css is invisible. I NEED HELP THERE!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Juliette Lepan•150
    @jlepan
    Posted about 1 month ago

    Hi,

    I looked at the errors and here are some important points to fix:

    1.Issue with _base.css and GitHub Pages

    The file _base.css starts with an underscore _, and GitHub Pages uses Jekyll by default, which ignores all files and folders starting with _. So, this file is not published, causing the 404 error.

    To quickly test and fix this:

    • Rename _base.css to base.css (remove the underscore) in components/css/

    • Update the import in style.css accordingly:

    @import url('./components/css/base.css');
    
    • Then push these changes to GitHub and check if the error disappears.

    I’ve seen there’s another way by creating an empty .nojekyll file at the root of the repo to disable Jekyll, which would allow keeping the _base.css name and have GitHub Pages properly publish all files. You might want to look into that :)

    2. Issue with CSS layer names in heaer-overlay.css

    In that file, there is:

    @layer component {
      /* styles */
    }
    

    Whereas in style.css, the layers are declared as:

    @layer base, components, utilities;
    

    The layer name is components plural, not component singular.

    As a result: The styles in heaer-overlay.css don’t apply correctly because they’re in a different layer.

    You should either change heaer-overlay.css to:

    @layer components {
      /* styles */
    }
    

    Or add component to the layer declaration in style.css.

    I hope this helps you fix the issue, good luck!

    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