Skip to content

React Decompose solution#4303

Open
LisandraCaniato wants to merge 1 commit intomate-academy:masterfrom
LisandraCaniato:master
Open

React Decompose solution#4303
LisandraCaniato wants to merge 1 commit intomate-academy:masterfrom
LisandraCaniato:master

Conversation

@LisandraCaniato
Copy link

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

Excellent work on this task! Your solution is approved because you've successfully met all the core requirements. You did a great job splitting the application into Header, Welcome, and Article components and correctly separating the CSS into component-specific files. As a suggestion for future improvement, consider extracting the navigation logic from the Header into its own Navigation component. While this was an optional step, it's a great practice for creating more modular and reusable code. Keep up the fantastic work!


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

Footnotes

  1. Rate AI review example

</p>
</article>
<Welcome />
<Header />

Choose a reason for hiding this comment

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

Good job splitting the main components! As a next step for better decomposition, consider extracting the navigation logic from the Header component into its own Navigation component. The task description mentions this as a possible improvement.

Comment on lines +21 to +28
.navigation__link {
display: inline-block;
outline: none;
text-decoration: none;
opacity: 0.7;
padding: 0 0.5em;
color: black;
transition: opacity 0.2s ease-in-out;

Choose a reason for hiding this comment

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

These styles are related to the navigation part of the header. The task description suggests that you could create a separate Navigation component. If you do so, these styles should be moved to their own Navigation.css file to improve modularity.

Comment on lines +8 to +20
<nav className="navigation">
<a className="navigation__link" href="#about">
About
</a>

<a className="navigation__link" href="#services">
Services
</a>

<a className="navigation__link" href="#contact">
Contact
</a>
</nav>

Choose a reason for hiding this comment

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

Good work creating the Header component. As a next step, you could move this <nav> block into its own Navigation component. The task description suggests this as a way to further decompose the application. This practice improves modularity and makes the Navigation component potentially reusable elsewhere.

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