docs: add topology-based project structure decision tree#7517
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
|
/gemini review |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the project structuring documentation by adding a "Decision tree: pick a structure by topology" section. This section includes a table that provides recommendations on whether to use a single project or multiple projects based on business topology, such as team ownership and product context. I have no feedback to provide.
Address Matt's review comment: "Splitting later is reversible" reads as if the act of splitting could be undone, which isn't true. Replace with a clearer call-to-action that drops the splitting/merging tangent.
2 participants
Summary
structuring-your-projects.md, placed between "Understanding Flagsmith's data model" and "When to create separate projects".Closes #7507.