Skip to content
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

Merged
merged 21 commits into from
Aug 2, 2023
Merged

Update and restructure content #840

merged 21 commits into from
Aug 2, 2023

Conversation

alexandratran
Copy link
Contributor

@alexandratran alexandratran commented Jun 29, 2023

  • Restructure content to de-emphasize beginner/generic dapp content and highlight SDK as recommended method. Add recommended topics for beginners vs experienced devs.
  • Add and edit some related conceptual content. See more in these PRs: Add web3 architecture diagram #859 Separate concepts out from reference #860
  • Rephrase and reorganize some topics to be more task-oriented
  • Update various links, file names, configuration, and redirects

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/

@alexandratran alexandratran requested review from a team and ziad-saab as code owners June 29, 2023 06:28
@github-actions
Copy link

Preview published: restructure

@github-actions
Copy link

Preview published: restructure

Copy link
Contributor

@rajkaramchedu rajkaramchedu left a 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.

@github-actions
Copy link

Preview published: restructure

@github-actions
Copy link

Preview published: restructure

1 similar comment
@github-actions
Copy link

Preview published: restructure

@github-actions
Copy link

github-actions bot commented Jul 6, 2023

Preview published: restructure

@github-actions
Copy link

Preview published: restructure

Proposing some minor copy adjustments
@github-actions
Copy link

Preview published: restructure

README.md Outdated Show resolved Hide resolved
@vandan
Copy link
Contributor

vandan commented Jul 18, 2023

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.

@github-actions
Copy link

Preview published: restructure

@github-actions
Copy link

Preview published: restructure

@alexandratran
Copy link
Contributor Author

alexandratran commented Jul 18, 2023

@vandan

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.

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
---

Copy link
Contributor

@BelfordZ BelfordZ Jul 18, 2023

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

Copy link
Contributor Author

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!

Copy link
Contributor

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.

Copy link
Contributor Author

@alexandratran alexandratran Jul 18, 2023

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.

@github-actions
Copy link

Preview published: restructure

@github-actions
Copy link

Preview published: restructure

@BelfordZ
Copy link
Contributor

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.

@github-actions
Copy link

Preview published: restructure

@github-actions
Copy link

Preview published: restructure

@alexandratran
Copy link
Contributor Author

@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.

@vandan
Copy link
Contributor

vandan commented Jul 18, 2023

@vandan

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.

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?

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.

@github-actions
Copy link

Preview published: restructure

@github-actions
Copy link

Preview published: restructure

@vandan
Copy link
Contributor

vandan commented Jul 27, 2023

@shanejonas I assigned you to this one to share any thoughts you have on the adjusted content structure.
(there's not as much to technically review, but I thought you might be interested in the new onboarding paths)

Copy link
Contributor

@vandan vandan left a 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.

@alexandratran alexandratran merged commit 266a770 into main Aug 2, 2023
11 checks passed
@alexandratran alexandratran deleted the restructure branch August 2, 2023 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants