LAZUR• 60
@Lazur05
Submitted
What are you most proud of, and what would you do differently next time?
This was my first time to use the BEM method, it helped me a lot to have cleaner code and I will use it more often
P
Fırat
@firatyedibela
All comments
- Agung Prasetyo• 40
@agpprastyo
Submitted
Great solution, good job!
Marked as helpful
0 - Matias Lombardi• 40
@Lombardimn
Submitted
What are you most proud of, and what would you do differently next time?
I am most proud of the component modularity achieved in this project. The
Card,Profile, andCallToActioncomponents are reusable, clean, and follow best practices in React development. This structure allowed me to easily add, remove, or modify parts of the card without affecting other areas. However, next time, I would focus on improving state management by incorporating React hooks, such asuseStateoruseContext, to handle dynamic data more effectively. Instead of hardcoding values, I would retrieve user profiles and social links from an external API, allowing the card to be more dynamic and adaptable.What challenges did you encounter, and how did you overcome them?
One challenge I encountered was handling CSS specificity and ensuring that styles applied correctly to each component. At times, styles conflicted or overrode each other. To overcome this, I used BEM (Block Element Modifier) naming conventions and scoped the styles within each component file. Additionally, using component-specific CSS files helped avoid global style conflicts. Another challenge was managing static assets like the avatar image, which I resolved by properly configuring file paths and ensuring they were bundled correctly in the build process.
What specific areas of your project would you like help with?
I would like assistance in implementing more advanced CSS techniques, such as animations or transitions, to enhance user interaction. Additionally, help with improving the project’s state management, especially handling asynchronous data from an API, would be valuable. I'd also appreciate guidance on how to better test components using Jest or Testing Library to ensure the robustness of the application as it grows.
The solution includes semantic HTML elements like <a> tags, which help with accessibility by providing a clear structure.
Users can navigate through interactive elements easily using their keyboards.
On devices smaller than 350px, the card touches the screen edges. Maybe adding a little extra space could help it look nicer and easier to read.
Other than that, the solution matches the design, and looks good.
Good job! Keep up the great work!
0 - Aparna Dhara• 130
@AD9-1
Submitted
Good job on the Blog component!
-
The solution matches the design and looks great.
-
The layout looks good on both desktop and mobile screens.
-
One suggestion I have is to consider using semantic HTML elements like <article> for the blog post container instead of <div>. This enhances accessibility for screen readers and is beneficial for SEO.
-
Additionaly, instead of hardcoding the content, you could pass it as props to make the Blog component more reusable.
This way, you can easily create multiple self contained blog posts without duplicating code.
Keep up the great work!
0 -
- Eduardo• 40
@MrRedu
Submitted
The solution matches the design and looks great.
Please consider providing the code too.
Marked as helpful
0
