What is this bug about?

When we bootstrap the chat demo application by npx wolkenkit@4.0.0-internal.108 init, the client uses old API routes, causing a 404 error.

What is the expected result?

When we bootstrap the chat demo application, it works as-is.

What is the actual result?

The chat demo application is not usable, since the client can't fetch from the back-end.

I would like to review the docs and explain also de concepts behind some decisions.
Things needed to explain:

• DDD objectives and reasons why.
• Core concepts like
  • bounded context
  • anti corruption layer
  • domain
  • value objects VS entities
  • aggregates
  • aggregate root
  • layered architecture and each one responsibility
  • reasons for the command and query bus
  • the even

When someone changes their vote on a comment or post, we need to update the view.

Currently, we have to refresh the browser to see the changes.

On upvote:

• if the user hasn't already upvoted, it should be +1
• if the user already upvoted, it should stay the same
• if the user downvoted, it should + 1

On downvote:

• if the user hasn't already downvoted, it should be -1
• if t