Builders reorg

[eshaben]

Description

This PR is built on-top of the Moonbeam vs Ethereum changes PR as a way to hopefully make the review process a bit easier: #888

This PR adds a page on creating an account, moves the Eth JSON RPC and Moonbeam JSON RPC content to the "Interact with the Network" section (name subject to change), and also renames some of the other sections in the Builders section.

Section index page icons are here: papermoonio/moonbeam-mkdocs#181
⚠️ will need to update the mkdocs PR to include redirects

Checklist

• I have added a label to this PR 🏷️
• I have run my changes through Grammarly
• If this requires translations for the moonbeam-docs-cn repo, I have created a ticket for the translations in Jira
• If pages have been moved around, I have created an additional PR in moonbeam-mkdocs to update redirects

Corresponding PRs

Please link to any corresponding PRs here.

After Translation Requirements

• Will need to create PR in moonbeam-mkdocs repo to add redirects for Chinese site

[eshaben]

Maybe need to consider whether the Debug and Trace and Event Subscription pages should be moved

[albertov19]

Hey! General notes:

1. I believe the trace should be moved to Interact because tracing is actually a new JSON RPC spec
2. The Interact With Network logo in the dropdown should change
3. What about having a Dropdown for "JSON RPC API" and then have three separate things " Standard Ethereum", "Tracing Ethereum", "Custom Moonbeam" or something like that?
4. One thing that is Weird in Development Toolkit is that it feels empty. Maybe we can create a "Ghost" section of Cross-Chain that points to places in the Interoperability docs?
5. I feel that with our new structure, the left hand side menus loop a bit empty. Maybe (just an idea) we can have, in each section, a Tutorials section where we show how to use relevant stuff of that section? Wdyt? This would mean we scrap the tutorial section that currently exist.

[themacexpert]

LGTM 👍 just a couple quick things

[albertov19]

I think this looks good.

I left some comments and suggestions, let me know what you think!

[albertov19]

I'm not fond of this title because it looks weird in the dropdown menu:

Like a development toolkit, it also works to interact with the network, the same as for JSON RPC stuff.
I think this title has to answer the question "How will developers click here? What are they looking for?"

We should do some brainstorming around this

[eshaben]

Yeah, would love some suggestions 🙂

[albertov19]

Ok so maybe we can do something like "Unique Features"? And actually segment a bit more the precompile section so that there are multiple subsections like:

"
Precompiles:
|- Native Ethereum
|- User Experience
|- Interoperability
|- Network Features

"

Maybe not "Unique Features" but something like that?

[eshaben]

What about "Development Interfaces" - I actually really like this, feel like I finally found something I feel good about.

As for breaking up the precompiles section, I feel like this is opening another can of worms. But tried to come up with a couple of suggestions:

OPTION 1 (driving factor behind this option: I feel like certain precompiles should have higher visibility, this grouping makes it easier to understand there are several precompiles involved throughout the governance process, etc.):

Account Management
├─ Identity
└─ Proxy
Author Mapping
Ethereum Compatibility
├─ Ethereum MainNet
└─ ERC-20
Governance
├─ Collective
├─ Conviction Voting
├─ Preimage
└─ Referenda
Interoperability
├─ GMP
├─ X-Tokens
├─ XCM Transactor
└─ XCM Utilities
Staking
Randomness
User Experience
├─ Batch
└─ Call Permit
Utilities
├─ Precompile Registry
└─ Relay Data Verifier

OPTION 2 (driving factor: to categorize the precompiles so they are easier to find, however, there are more clicks for certain items and less visibility, but perhaps slightly more organized than option 1):

Ethereum Compatibility
├─ Ethereum MainNet
└─ ERC-20
User Experience
├─ Batch
└─ Call Permit
Utilities
├─ Author Mapping
├─ Precompile Registry
└─ Relay Data Verifier
Network Features
├─ Governance
│   ├─ Collective
│   ├─ Conviction Voting
│   ├─ Preimage
│   └─ Referenda
├─ Identity
├─ Interoperability
│   ├─ GMP
│   ├─ X-Tokens
│   ├─ XCM Transactor
│   └─ XCM Utilities
├─ Proxy
├─ Staking
└─ Randomness

I prefer the first option, as it adds some organization making certain precompiles easier to find and it also maintains visibility of the precompiles (not having items too nested), but it could maybe benefit from some changes; what those changes might be is what I am unsure about

[albertov19]

I do like this new title, but it feels weir that we don't have an "Ethereum API".

So maybe by changing the "Interact with the Network" title to something more relevant like "Unique Interfaces" or IDK we can just have "Ethereum API" and "Substrate API" (With Ethereum coming first?)

[eshaben]

Yeah, I get what you're saying. I think there is value in keeping "Precompiled Contracts" though - what about "Substrate Interfaces" or "Substrate Module Interfaces"?

[albertov19]

LGTM