Feature request: project structure improvement

So, I wanted to dive into this, but honestly for longer community maintained development this seems like an absolute hassle. Why not get a little bit of inspiration from e.g. https://github.com/unslothai/unsloth/tree/main/studio and then connect relevant services together instead of having 30 modules in a directory? This can work for fully agentic development but I still believe there is a good reason for having a little bit of isolation around here. Example for everything: -> why do we have source directory with separate services and core and mcp servers and routes? Why is there no clear distinction between what's frontend, what's backend? I skimmed static directory and it seems like that's where the actual frontend code lives which is.. mildly confusing. If so, why plain JS and how are we handling state without loosing our minds? No wonder one of "todos" is to improve visibility. I think making the repo more maintainable so further people can build on it should be a first step before it'll become even messier. I am happy to give guidance/work on it, if maintainer hits me up. Obviously such refactor would mean most of the PRs before it are gonna be rendered moot. I am writing this not as a jab, but as someone who wants to send patches but got stunned by the structure :D