Future developments

[MaelVB]

The strong point of AquilaCMS is its end-customer-oriented vision, which currently provides a large number of native functionalities.
The downside is that it lacks a development framework that is practical and attractive enough for today's developers.
Over the next few months, we'll be sticking to current web development best practices:

• Add a logger (Winston with Morgan) and manage sending to Graylog
• Dependency management via workspaces [scheduled for November]
• Refactor branch management to match Trunk Based Development [scheduled for November]
• Refactor repo file organization to match monorepo style [scheduled for December]
• API v3 in Nest started [scheduled for June]
• A brand new backoffice [scheduled for September]
• Rework module architecture
• Use of a monorepo tool like Turborepo
• v2 and semver
• Update deployment files
• Start converting the project to TypeScript
• Consider more modern dependencies (Hono instead of Express for example)