Transaction graph and docs cleanup #521
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
JumiDeluxe
force-pushed
the
docs-graph-cleanup
branch
2 times, most recently
from
942855e to
b8b0636
Compare
JumiDeluxe
force-pushed
the
docs-graph-cleanup
branch
from
b8b0636 to
f1e5321
Compare
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.
Yesterday @piotro888 showed me transaction graph that is generated in docs with use of
mermaid.It was very small, but we noticed that it is readable (blocks, connections are still a mess but that is another issue) zooming in a lot.
I've scaled the graph and added scrolls to temporarily fix the graph problem, until someone fixes generation.
It looks quite good on mobile too and
ctrl+Fa phrase makes graph scroll to search result which is nicePreview:
Mobile preview:
Also I've changed documentation files naming to kebab convention for consistency and better UX
(connected issue: #216)