Skip to content
OverviewSolutions
111
Comments
47
P
Karol
@VillageR88

All comments

  • Alex 🤸🏻‍♂️•1,490
    @sksksk2024Submitted 3 days ago
    What are you most proud of, and what would you do differently next time?

    The key takeaways I will gain from completing this project:

    • Gaining a deeper understanding of fetch, which I'm still getting familiar with.
    • Improving my knowledge of background styling in pure CSS.
    • Enhancing my skills in styling and positioning, which still takes me the most time.
    • Becoming more accustomed to developing logic independently, focusing on structure, error handling, fetching, and other key aspects.

    API Link Shortener 🔥sksksk🔥

    #accessibility#fetch#react#tailwind-css#daisy-ui
    2
    P
    Karol•2,460
    @VillageR88Posted 3 days ago

    Alex, you're doing a great job! However, take a look at the main element on most common websites, it's almost always limited to a max width of 1440px or 1110px. You might want to consider that for better consistency.

    Marked as helpful
    2
  • P
    Karol•2,460
    @VillageR88Posted 4 days ago

    Good work! However, on larger monitors, the two containers seem too far apart. Consider adjusting the spacing for better balance.

    Marked as helpful
    0
  • P
    Karol•2,460
    @VillageR88Posted 4 days ago

    Tip 🔗

    Marcin, I noticed your previous challenges seem to be overwritten by the current one. Do you need help with this?

    Marked as helpful
    0
  • Alex 🤸🏻‍♂️•1,490
    @sksksk2024Submitted 5 days ago
    What are you most proud of, and what would you do differently next time?

    I’ve gained a ton of experience over the past few days of hard work. I dove deep into the logic and integration of MongoDB with the front-end, which was definitely the most challenging part for me. It’s amazing to realize that deploying a full-stack app is now second nature to me, thanks to the hands-on experience I gained (took me just 20 minutes, instead of 1-2 days, to nail it 💥). Feel free to check it out—it's the most complex project I've done so far, and I’m super proud of how it turned out.🔥

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

    I am figuring out now how to make that fav-icon working. I don't know why in local works, but in here isn't. Feel free to add any advice to my work. Thanks in advance! 🙋‍♂️🔥

    Filter for your favourite place MERN 🔥sksksk🔥

    #accessibility#node#react#tailwind-css#redux-toolkit
    1
    P
    Karol•2,460
    @VillageR88Posted 5 days ago

    Great to see you making progress and tackling challenges like integrating MongoDB with the front end. It's a solid step forward in building your skills. Keep refining your work, there’s always more to learn. Good luck with your projects!

    1
  • P
    Karol•2,460
    @VillageR88Posted 9 days ago

    I just came across your profile, and I have to say, your work in frontend development is outstanding. You're like the top 1% of this community, doing an amazing job.

    Marked as helpful
    0
  • Alex 🤸🏻‍♂️•1,490
    @sksksk2024Submitted 11 days ago
    What are you most proud of, and what would you do differently next time?

    The accomplishments I’m most proud of are:

    • I’ve started to enjoy creating website layouts more and no longer find it boring.
    • I now have a better understanding of positioning images effectively, whether it's aligning them to the right, left, or specific corners of a layout.
    • I've learned to use Lighthouse to identify a website's weaknesses. For instance, in my case, I already knew the issue: images without fixed width and height. While I prefer this approach, it’s a valuable tool to check a site’s speed and performance! I’ve come to terms with the fact that I can’t avoid useEffect as easily as I’d like. In this case, though, it proved incredibly useful, and now I feel much more confident using it.
    • I’ve overcome the frustration of not being able to stick images to the edges. It turned out the issue was dynamic width and height causing inconsistent positioning—an insight that has greatly improved my layouts.

    Insure Real Deal Security 🔥sksksk🔥

    #accessibility#lighthouse#pure-css#react#tailwind-css
    1
    P
    Karol•2,460
    @VillageR88Posted 11 days ago

    One suggestion, consider adding overflow-x: clip; to your body element. This will prevent horizontal scrolling when content overflows the viewport width, ensuring a cleaner layout.

    Marked as helpful
    1
  • P
    Karol•2,460
    @VillageR88Posted 24 days ago

    Tip 🔗

    0
  • P
    Karol•2,460
    @VillageR88Posted 26 days ago

    Looks like you messed up your whole repository. Need some help fixing it?

    I recommend setting up each solution as a separate deployment using GitHub Actions, rather than deploying everything to your main profile

    0
  • P
    Karol•2,460
    @VillageR88Posted 28 days ago

    Pro 👍 Don't forget to check the console.

    0
  • P
    Karol•2,460
    @VillageR88Posted 28 days ago

    Great visual progress. You're improving with every challenge 👍! Just a quick reminder to check the console for any errors.

    0
  • SEBAANA YUSUF SALIM•140
    @salehjosephSubmitted 29 days ago
    What are you most proud of, and what would you do differently next time?

    Here are some code snippets I'm proud of:

    How did we do?

    .rating button:hover {
  background-color: hsl(0, 0%, 100%);
  color: hsl(216, 12%, 8%);
}

    submitButton.addEventListener('click', () => {
  if (selectedValue > 0) {
    selectedRating.textContent = selectedValue;
    ratingState.style.display = 'none';
    thankYouState.style.display = 'block';
  } else {
    errorMessage.style.display = 'block';
  }
});
    What challenges did you encounter, and how did you overcome them?

    Bringing out the exact design without a Figma file was hard, I just tried to do what I could though I believe the results ain't bad

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

    Still having a problem with how event Listeners work in the DOM

    interactive rating component Using HTML, CSS and JavaScript

    1
    P
    Karol•2,460
    @VillageR88Posted 29 days ago

    Your implementation works well for a mockup, and the interactive behavior is clear. However, it doesn't fully align with real-world development practices.

    Form Structure: In real applications, the submit button should be nested inside a <form> element. This approach ensures proper submission behavior, follows standard web patterns, and improves accessibility.

    Server Communication: Instead of only toggling frontend states, you could set up the form element's action attribute to submit the feedback to endpoint. This makes the functionality closer to real-world form handling.

    0
  • P
    Karol•2,460
    @VillageR88Posted 30 days ago

    No media queries in CSS – no responsive design.

    0