I guess you can remove this now 🙂 See https://syllabus.codeyourfuture.io/guides/marking-guide#commented-out-code

While most browsers will handle a back slash (\) as a separator in URLs, it's convention to use a forward slash /.

You can remove this commented out code as you're no longer using it. You can always see the history of this file in Git if you need to. Alternatively, if you want to keep it around, consider storing it in a separate file outside of your repo. See https://syllabus.codeyourfuture.io/guides/code-style-guide#dont-leave-lots-of-commented-out-code for more info

It looks like you missed this closing tag when commenting out the block above - it can be removed along with the commented out code.

As an extra note, this extra closing tag affects the validity of the HTML page. Browsers are usually quite forgiving, and this probably won't cause any visual or functional issues with your page, but it will stop Prettier from formatting your code - Prettier can only format your code if it is valid. If you remove this closing tag and then run the "format document" command in VSCode with this file open then you'll see several changes occur, like extra spaces being removed, indentation changed, etc. You can run the format document command with ctrl + shift + p (or cmd + shift + p if you're using a Mac), then type format document and hit enter. If you've set up VSCode as described here then this should happen automatically when you save your code.

The css folder should contain css files only - you can keep this HTML file in the root of the project, along with index.html.

I'd also suggest naming danti.css and danti.html store.css and store.html to make it obvious what they provide 👍

If you do follow my other comment and include style.css on the store page, be aware that you have a rulset in that CSS file for .contener as well. If you want them to do different things, you'll need to give them different class names.

There's usually only one <main> element on the page, used for the primary content area. There are several other semantic elements you could use to "section" your content. This part of the week 1 lesson should have everything you need 🚀

Remember every image need an alt attribute which should attempt to provide equivalent meaning for users of screen-readers and other assistive technologies. In this case, it's a logo, so useful alt text would be the name of the company, Karma.

You linked the button in the new page section to the store page, just need to update this item to link to the store as well 👍

This should probably be a h2, because there's no h2 for this to be a sub-heading of. See https://syllabus.codeyourfuture.io/html-css/week-1/lesson#text-content

The h4 below probably doesn't need to be a heading at all - it can be a paragraph (<p>) or <span> and you can style it to be the right font size, etc.

See https://www.w3schools.com/html/html_headings.asp for an overview of how and when to use headings, and why it's important to only use them when the text really is a heading (and not just "big text").

A nice accessibility pattern for navigation menus is to use a list within the <nav> element:

you can add rules in your CSS file to remove the default browser "bullet point" styles like this:

.nav_ul ul {
  margin: 0;
  padding: 0;
  list-style: none;
}