jofaval / babylon Goto Github PK

• Fix the first line, Github Project is not properly qritten
• Add the initial date I stars writting down some ideas
• Also add a relative initial date I might of thought of the idea

Or OpenAPI specification

No versions have been defined, so let's define the versioning criteria and, after the initial tasks (#3) have been defined, assigne them to a version

Maintain some sort of logic than can actually create a monorepo from all of the other services using Turborepo and some copy and paste or cloning (automated, obviously) from the other repos. As to have the other option if it won't cause too much trouble that is.

Just an idea that could actually be really fun and intresting to explore. And challenging maybe, hopefully (in a good way tho).

If done, use git submodules for the linking, Git - Submodules, or better even, Git subtrees

Just a general grasp of the services and it's entities, maybe more sort of like a Service diagram, I'll rethink it, and each service should have it's own independent EER Diagram

Self-descriptive, but more detail should be added

Define each service, the CHANGELOG (it'd be nice that it could be updated automatically in some sort of way, replcating an existing CHANGELOG or creating a new one from merging the other repositories).

A little description about the project, and it'd be a plus to have the architecture design & choices up there too!

Keycloak will be the main user identifier, access, autheticantion, guard control for the platform

Just initialazing the Github Project with the Feature template, but modifying it so it uses versiosining instead of iterations.