-
Notifications
You must be signed in to change notification settings - Fork 288
Add Nexus adoption decision tree to evaluate nexus page #4123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📖 Docs PR preview links
|
|
|
||
| Use the following decision tree to help determine if Nexus is right for your use case: | ||
|
|
||
| <div style={{textAlign: 'center', margin: '2rem 0'}}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about making this a component? We could definitely reuse this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple comments on the image:
- Does
namespacesneed to be capitalized to match other parts of the docs? - I don't quite understand what
Is cross-x support is a future goal and not time critical?means? Could this be rephrased?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think we should use excalifont -- they are hard to read and not super accessible. do we have a style guide for diagrams? we should make one if we don't to make sure they are consistent across the site
this diagram is already complex, so i think we should opt for cleaner fonts
What does this PR do?
Notes to reviewers