[Docs] Describe Sylius architectural drivers #14197
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Zales0123
added
the
Documentation
lchrusciel
approved these changes
Aug 1, 2022
Roshyo
approved these changes
Aug 11, 2022
|
Thanks, Mateusz! 馃 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We've already started documenting some of the architectural decisions with ADRs. I believe it's also very important to describe what is driving us into certain decisions, to make them more comprehensible for everyone using Sylius.
Obviously, this new chapter is just a beginning and I strongly feel we would have to spend some time there to make it great. Let's start simple and then think about possible improvements 馃枛