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

Kanban task manager - Next.js + Spring Boot + AWS (2 separate repos)

next, react, postgres
Ivan Olmo•310
@ivanolmo
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?

There are no tags for Java, Spring Boot, Docker, or AWS, but this project uses each of those. Also, there is only room to list one repo, so the one I listed is the Next.js frontend. The backend Spring Boot repo is at:

https://github.com/ivanolmo/kanban-spring-backend

Info

I finished this project last year but forgot to upload my solution here. I used Next.js for the frontend, Java/Spring Boot for the backend API, and AWS for backend hosting and an RDS Postgres database. The backend API is running in a docker container on an ec2 instance. I also used this app for a school project, so it has a couple additional features, including auth, search, and report generation.

Logging in

The frontend is using NextAuth and requires you to create an email/password account to sign in. If you want to check it out but don't want to create anything, here are some test credentials:

email: test@test.com

password: asdf

Most proud of

Is this overengineered for what it is? Absolutely, but I wanted a quick way to get some hands-on experience with Spring Boot since I had a client that needed some work done on their existing system. I built a previous version of this same application using full-stack Next.js with tRPC/Prisma for the backend logic. That was fine, but in my location, Java and Spring Boot are still huge. I guess what I'm most proud of was getting up to speed with all the basics of a major framework pretty quickly (Java is absolutely not dead).

What I'd do differently

The only thing I'd probably do differently next time is to write some tests before writing code. Actually, I'd also do a little more planning using pen and paper instead of jumping into the code right away, too.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ivan Olmo'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.