chore(docs): add feedback loop and code re-use to Why Nexus #725
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.
As mentioned in #585
These are some of the benefits that I mentioned.
I think most of the gist of the initial issue is now in the docs. I extended the section with what I personally think are two of the major benefits of going to a Code first approach and especially using Nexus:
The one thing which I think still deserves a highlight is the "endless" possibilities with plugins. I tried to hint at it in the context of repetitive work but in fact plugins can do way more. But I wasn't sure on how to fit it in or word it properly.