The advantage of a monorepo over a lot of smaller repositories is that you can make changes across your entire codebase at once. A new feature might involve add

The advantage of a monorepo over a lot of smaller repositories is that you can make changes across your entire codebase at once. A new feature might involve adding a new api in /api, and updating the mobile apss in /android and /ios, as well as the webapp in /app. You might also mention the feature in the documentation (/docs), as well as the website in /www, and so on. All of those changes happen as part of a single merge to master (or whatever branch system you prefer) and are discussed in a single issue. Simplicity is the whole point, so you just assign the whole issue to a milestone and you're done.