Idiomatic monorepo setup

[mitschabaude]

There are some excellent proposals made here by @sam-goodman for how to improve the monorepo setup with separate contracts/ and ui/: https://github.com/o1-labs/o1js/issues/1576#issuecomment-2054190363

Configuring workspaces (probably npm workspaces?) and TS as described in that comment seems like a major improvement over the flow of locally npm-linking subdirectories that we recommend in our docs: https://docs.minaprotocol.com/zkapps/how-to-write-a-zkapp-ui#local-development

• npm link is an extra step that is easily missed, and it breaks the usual expectation that everything needed to develop is part of a repo and shared between developers explicitly
• It's bad practice to override behavior globally on your machine, as npm link does

Alternative

A different way to approach this would be to move contracts and UI into the same project. Pro: it's simpler. I don't have a good sense of the trade-offs there tbh, should ask existing developers for their preferences

[ymekuria]

Configuring workspaces (probably npm workspaces?) and TS as described in that comment seems like a major improvement over the flow of locally npm-linking subdirectories that we recommend in our docs: https://docs.minaprotocol.com/zkapps/how-to-write-a-zkapp-ui#local-development

We need to revisit this and probably move away from recommending npm link as the workflow.