-
-
Notifications
You must be signed in to change notification settings - Fork 947
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
Update and restructure content #840
Conversation
Preview published: restructure |
Preview published: restructure |
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.
Looks and reads great.
Preview published: restructure |
Preview published: restructure |
1 similar comment
Preview published: restructure |
Preview published: restructure |
Preview published: restructure |
Proposing some minor copy adjustments
Preview published: restructure |
Developers following the "Get started building a dapp" path from the home page are led to a pretty confusing sequence that doesn't match the description. By taking them to setup steps, that content doesn't lead them to the tutorial where they actually build a dapp. We should either revert by sending them to the tutorial where there can be references to the pre-requisite setup steps or establish more linkage between the setup steps and the tutorial. |
Co-authored-by: Vandan <[email protected]>
Preview published: restructure |
Preview published: restructure |
The first paragraph in the first page of the "Get started building a dapp" section refers explicitly to the tutorial: https://docs.metamask.io/restructure/wallet/how-to/get-started-building/set-up-dev-environment/ Is this not enough linkage? Also, in our docs, "Get started building a dapp" refers to the beginner/general dapp setup content, which is separate from the more MM-specific content (as described in the MM dev docs restructure proposal). Can you expand on what is a confusing sequence / what doesn't match what description? |
--- | ||
sidebar_position: 1 | ||
--- | ||
|
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.
Are we able to make this autogenerate the cards / items below with a simlar file as wallet/how-to/connect/category.json ? Not sure, but I'd imagine that the description
part of the _category_.json
would support markdown. The only thing that would be missing would be the note at the bottom I think?
reference: https://docusaurus.io/docs/sidebar/autogenerated#autogenerated-sidebar-metadata
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.
The autogenerated category cards by default don't support displaying bulleted lists with different links, which is the primary need for this page.
I slightly modified the style of the SDK cards to better match the category cards. Let me know if there's a better solution!
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.
Ah I see your point. It is quite nice to see all the items laid out. I think we can achieve the same thing while still using autogenerated indexes by 'swizzling' (more specifically ejecting) the DocCard
component or the DocCardList
component and modify it to display sub-categories differently (as a list, like you have it). That way it will benefit all the other autogenerated index pages.
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.
Swizzling those components to achieve what we currently have for the SDK would probably take me a long time to figure out, as I'm not experienced with React. Could we stick with my workaround for this PR and return to this issue in the future? Or if someone else is willing to experiment with that, or let me know of the specific solution, that's fine too.
Preview published: restructure |
Preview published: restructure |
Overall it looks great, and I like the structure / documentation guideline that you linked. The PR is a bit on the big side, making it more difficult to review. If possible, could you split out changes that aren't specifically required as part of this content restructuring? For example, perhaps changes like these could be split out to a seperate PR. |
Preview published: restructure |
Preview published: restructure |
@MetaMask/dev-ex I've separated out a few tasks into other PRs, and reverted those changes in this PR:
Hopefully that makes it easier to review. |
I see the reference to the tutorial now. Yeah, I was just expecting there to be a sequential flow that leads developers from setup to tutorial (for example if they just keep reading through each page and choosing "next"). I think it could be improved by highlighting the tutorial path at the end of setup steps vs mentioning it only at the beginning. |
# Conflicts: # wallet/how-to/display/tokens.md
Preview published: restructure |
# Conflicts: # wallet/index.md
Preview published: restructure |
@shanejonas I assigned you to this one to share any thoughts you have on the adjusted content structure. |
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've reviewed the content structure and copy changes. Overall these changes provide an improved set of paths for developers with distinct needs. The additional concepts sections are generally helpful to all developers as well.
This PR follows the MM dev docs restructure proposal.
(Note: it's easiest to do all restructuring and renaming files in one go, so we can simplify the redirects.)
Fixes #809
Fixes #808
Preview: https://docs.metamask.io/restructure/wallet/