Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

MENN Stack (MongoDB Atlas, Express, Nuxt.js, Node.js)

express, mongodb, node, nuxt, sass/scss
Chris Paschall•440
@ChrisP1108
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


This is the first full stack app I've build. This project was definitely a challenge but I definitely learned a lot in doing so, and pushed myself by fulfilling all the bonus challenges.

The technologies I used on the front end was Nuxt.js, a framework for Vue.js, and Sass CSS pre-processor. I utilized Vuex for state management, along with typescript for the vuex store, although I didn't utilize typescript directly in the Vue components, since I utilized Eslint which forced me to declare prop types anyway(and was pretty strict altogether about keeping the code organized a specific way before being able to make a git commit.) Sass definitely made it easily for me to keep the CSS organized and be able to style the light and dark mode color themes.

For the back end technologies I utilized MongoDB Atlas to allow cloud based storage, Node.js with express, Mongoose to connect Node.js with MongoDB, along with JWT (JSON web tokens), cookie parser for http only cookie storage of web tokens, along with Bcrypt for secure storage of passwords utilizing a hash algorithm. So anyone who may feel skeptical about registering a password, don't worry, the Bcrypt hash algorithm makes your password storage safe. The backend was setup with a REST API with all the routes except for login and registering a user being protected, so only the user who created specific boards/tasks can access them.

The most difficult part of this whole project was setting up error handling, given that its a full stack app, to prevent a user from being able to do things such as register the same username that another user has, or being able to name two boards or two tasks within the same board the exact same name, and also set up for when in those rare instances when something goes wrong to have an error modal popup letting the user know that their changes weren't saved.

The second challenge I had was being able to drag and drop tasks from one column(status) to another and getting it to perform smoothly. Although it does work, I was hoping to be able to improve on it better, but to no avail. It could be because of all the event listening going on with the mouse movements, mousedown, mouseup handlers. If anyone has ideas on how to improve the performance of this, let me know.

I've added additional features on top of the UI design, mainly being user accounts.

If anyone has any ideas on how I can improve this app, let me know.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Chris Paschall's solution.

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 1st-party linked stylesheets, and styles within <style> tags.

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.