Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 months ago

Kanban task management web app with vanilla HTML, CSS and JS

Michael•150
@ristoranteQF
A solution to the Kanban task management web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm not proud of shit. I'm not satisfied with the structure of my code, it is not well organised, it is chaotic and probably in a month I will also forget what the hell I wrote in there. xD

At least this app is functional.

Next time I would really think about the structure of my code so that I can make it more modular, readable, clean and separate concerns.

What challenges did you encounter, and how did you overcome them?

I encountered a few logical bugs and synchronizing the api data with the ui after each interaction. I simply used AI because otherwise I would have probably lost my mind and finish the project in at least a month. xD

I'm not looking to cheat with ai, I simply view this as a very useful tool that helps me learn faster right now because I'm a beginner.

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

I would like to get help on the structure of the code. I want to separate concerns and have a clean code following this pattern: API data functionality, logic functionality and UI rendering.

Also, there is still a small bug on the rendering aspect. The code won't sync the left subtask count ui in each task card with the api data after relevant interactions.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nathan Molina•280
    @Natentado
    Posted 3 months ago

    I think you jumped a few steps on your learning, trying challenges like achieving this kind of project with pure js its a good thing but not when you need to reinforce your fundamentals first, like you js file has more than 1,300 lines of code and most of them are redundant, so i have a few tips for you:

    • Roll back to less hard challenges (junior/intermediate).
    • Reinforce Css like:
      • Variables
      • Responsiveness
      • BEM or other patterns
      • CSS performance
    • Reinforce some logical fundamentals like:
      • DRY pattern
      • Components
      • Separation of concerns
      • Code splitting
    • Then choose a js Framework to learn along advanced js patterns like:
      • React
      • Vue
      • Angular

    After more study and projects maded, i think you can adventure to advanced and guru challenges from this platform and ace it like pro without the necessary need of AI, or just to help you with things you already know or worked with it before

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub