Add ADR for organizing our folder structure in a feature-based manner #296
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is linked to issue openedx/frontend-app-authoring#1239 .
context:
We would like to improve our folder structure to make it more scalable and to separate redux for "framework" purposes - like saving xblocks - from redux for internal editor state. We want to organize our redux better and also organize our components by feature, rather than just keeping them deeply nested in some parent component folders. (read more about all of this in the issue linked above.)
The ADR is not one I have created. It is an ADR used by many openedx-repositories and based on community best practices. We want to review it, and if accepted, adopt it.
Later, not as part of this PR, we would like to add our own, second, ADR that is very specific to this repository and decides more of the "how" to implement what this feature-based organization ADR recommends.
This should be reviewed by our whole team and requires everyone's approval.