[Docs] Diagram visualization of the rexmex project#62
Open
ivanmilevtues wants to merge 1 commit intoAstraZeneca:mainfrom
Open
[Docs] Diagram visualization of the rexmex project#62ivanmilevtues wants to merge 1 commit intoAstraZeneca:mainfrom
ivanmilevtues wants to merge 1 commit intoAstraZeneca:mainfrom
Conversation
Author
|
Hey, a quick update on our side, this week we released our diagram generaiton engine as an open-source project! If you are interested to see more on how the generation works you can do so at https://github.com/CodeBoarding/CodeBoarding |
This file contains hidden or 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
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.
Summary
In this PR I am introducing diagram first documentaiton. You can see how it renders here:
https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/rexmex/on_boarding.md
The diagrams are designed so that people can quickly grasp the main flow of the project by seeing the main abstract components and how they interact with each other. There are a lot of scientists/researchers who interact with this codebase so I believe they are usually mostly interested in some particular part of the codebase. With these diagrams they can quickly navigate to that component and start editing it with the full context of the pipeline. Further most scientists are interested in the method and not as much in the codebase itself.
Would love to connect and discuss how we can help!
Any feedback is more than welcome! We have introduced a github action which will keep the docs automatically up-to-date with new changes, I'd love to integrate that for you if you are interested.
Full disclosure: we're trying to turn this into a startup, but we're still in a very early stage and figuring out what will actually be useful for people,
Not relevant:
Changes