Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add task solution #6068

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

add task solution #6068

wants to merge 2 commits into from

Conversation

Vanivnaa
Copy link

@Vanivnaa Vanivnaa commented Jan 31, 2025

  • DEMO LINK

  • TEST REPORT LINK

  • Header height is set in 1 place (for the links)

  • Content is vertically centered (for any header height)

  • CSS is used to show all letters in Uppercase (don't type them in HTML)

  • Logo is an image wrapped with a link

  • CSS Variable is used for a blue color

  • Pseudo-element is used for a blue line below the active link

  • Code follows all the Code Style Rules ❗️

Copy link

@mateacademy-ai-mentor mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


Thank you for your hard work on this project! 😊 While your code meets many of the task requirements, there are a few critical issues that need to be addressed before we can approve the pull request:

  1. CSS Class Naming: The class names do not follow the BEM naming convention, which is important for maintaining scalable and organized code. Consider renaming classes like .nav_ul, .nav_li, and .nav_item to better reflect their purpose and adhere to BEM principles.

  2. CSS Styling: Avoid using tag names for styling. Instead, apply styles using classes to ensure consistency and maintainability.

  3. HTML Formatting: Ensure that your HTML lines adhere to the 80-character limit for better readability and compliance with the checklist.

  4. Placeholder Links: The use of href="#" as a placeholder should be replaced with actual URLs or handled appropriately if intended for future implementation.

These changes are necessary to ensure the functionality and maintainability of your code. Once these issues are resolved, we can proceed with approving your pull request. Keep up the great work, and don't hesitate to reach out if you have any questions! 🚀

✨ Please rate this review in the Platform's notification center. I will be grateful for your feedback! ✨

🔄 Fix the issues, commit the changes, and then re-request my review using the Re-request review button in the Reviewers tab.

src/index.html Outdated
<header class="header">
<a
class="logo"
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated
<ul class="nav_ul">
<li class="nav_li">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated

<li class="nav_li">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated

<li class="nav_li">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated

<li class="nav_li laptops">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated

<li class="nav_li">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated

<li class="nav_li">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated

<li class="nav_li">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/index.html Outdated

<li class="nav_li">
<a
href="#"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The href="#" attribute is used as a placeholder. Consider replacing it with an actual URL or handling it appropriately if it's intended for future implementation.

src/style.css Outdated

.nav_item {
display: block;
align-items: center;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The align-items property is not applicable to block elements like .nav_item. Consider removing it or ensuring that .nav_item is a flex container if alignment is needed.

Copy link

@mateacademy-ai-mentor mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Summary

Great effort on addressing several issues from the previous review! 🎉 However, there are still some critical points that need attention to ensure your code is scalable and maintainable:

  1. CSS Class Naming: The class names such as .nav_ul, .nav_li, and .nav_item do not follow the BEM naming convention. Consider renaming them to something like nav__list, nav__item, and nav__link to adhere to BEM principles. This will help in maintaining organized and scalable code.

  2. CSS Styling: Avoid using tag names for styling, such as body and .nav_ul. Instead, apply styles using classes to ensure consistency and maintainability. This is crucial for avoiding conflicts and making your CSS more modular.

  3. HTML Formatting: Ensure that your HTML file adheres to the 80-character limit for lines. This will improve readability and make your code easier to manage.

Despite these issues, the decision to approve your pull request is made to help you move forward with your learning journey. Please take the time to review the comments and improve your code. Addressing these critical issues will help you avoid similar problems in the future. Keep up the good work and continue learning from these experiences! 🚀

✨ Please rate this review in the Platform's notification center. I will be grateful for your feedback! ✨

/>
</a>
<nav class="nav">
<ul class="nav_ul">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name 'nav_ul' does not follow the BEM naming convention. Consider renaming it to something like 'nav__list' to adhere to BEM principles.

</a>
<nav class="nav">
<ul class="nav_ul">
<li class="nav_li">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name 'nav_li' does not follow the BEM naming convention. Consider renaming it to something like 'nav__item' to adhere to BEM principles.

<li class="nav_li">
<a
href="https://www.moyo.ua/ua/brands/apple/"
class="nav_item is-active"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name 'nav_item' does not follow the BEM naming convention. Consider renaming it to something like 'nav__link' to adhere to BEM principles.

</a>
</li>

<li class="nav_li laptops">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name 'nav_li laptops' does not follow the BEM naming convention. Consider renaming it to something like 'nav__item nav__item--laptops' to adhere to BEM principles.

align-items: center;
}

.nav_ul {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name 'nav_ul' does not follow the BEM naming convention. Consider renaming it to something like 'nav__list' to adhere to BEM principles.

align-items: center;
}

.nav_li:not(:last-child) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name 'nav_li' does not follow the BEM naming convention. Consider renaming it to something like 'nav__item' to adhere to BEM principles.

margin-right: 20px;
}

.nav_item {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The class name 'nav_item' does not follow the BEM naming convention. Consider renaming it to something like 'nav__link' to adhere to BEM principles.

bottom: 0;
}

.nav_li a:hover {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid using tag names for styling. Instead, apply styles using classes to ensure consistency and maintainability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants