Migrate to true monorepo structure and dependencies

[glypse]

Currently the repo has a monorepo-like structure but no true monorepo tooling, making it awkward to transition this template to a true monorepo.

I propose we migrate the overall config to using a monorepo manager like nx or turborepo, making it easier to transition.

[66HEX]

Hey, this is because I didn’t want to assume from the start that Nx would be necessary. In the case of managing Motion Core—which is polyglot and partially written in Rust—Nx does indeed offer benefits; however, for Motion GPU, Nx would likely be overengineering.

Bun Workspaces was intended in this case solely to provide a separation between the documentation application itself and the package being documented.

Another thing is asking ourselves: where to draw the line between Motion Core’s opinion and agnosticism toward the broader community. Personally, I use Bun; perhaps someone else will use pnpm. The same goes for monorepos—if needed, I’d lean toward Nx, while someone else might prefer a turborepo.

[glypse]

I understand. I'd argue that bun can be replaced with pnpm with a single command, having that opinionated is fine, but if a user does switch to pnpm or npm, having a proper monorepo tool would be needed for cross-compatibility. Once a tool like Nx is set up, it doesn't cause much of a maintenance burden. Also, I find that in templates, it's much easier to get rid of a dependency at first use than to add a new system architecture (even though an experienced user could do both without an issue).

Overall, I would personally see a template, and especially this template since it's targeted at package documentation, as a ready-to-go monorepo starter. That's why I was thinking about making other issues about adding tools like commitlint, husky scripts that run format:check, lint:check and check-types, GitHub actions that runs those checks on pull requests, etc. That's personally what I would love of a template like this: a preconfigured everything setup.