-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Draft] Polkadot Development Overview (build) #4810
Conversation
You will probably find this useful: https://forum.parity.io/t/polkadot-substrate-cumulus-host-runtime-all-in-one-diagram/1836 And |
I would love to review this when final. The message here is crucial and we should adjust. This type of low level work can also use the opinion of a multitude of people, as it will be an important message. Who is --sort of-- the master mind behind the existing plan? On which page of the Polkadot website will this be hosted? Looking at the figure, one issue that I can spot is that you are using |
I believe it was one of the previous TechEd for the most current iteration, although I believe there were several peopel working on it over the years (@DrW3RK could clarify more probably).
For reference, this page currently lives here: https://wiki.polkadot.network/docs/build-guide. My hope is that it can serve as as good reference for any other pages which may benefit from defining these paths to development.
@kianenigma Once it is final, I'll request a review :) I agree, it is something that needs a lot more input and thought from everyone! And thank you for those resources, will implement them accordingly. |
Added some more content, removed repetitive stuff, and added the notion of four tracks:
Generally, I think a developer who (assuming knows nothing) could now more easily discern where they should go for learning depending on their goals. Some more graphics would be nice, as well as making sure it flows well. |
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.
Added conditional rendering, I noticed that there are still places with "Polkadot or Kusama". As the page is used for both wikis we need to make sure cponditional rendering is present.
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.
Added conditional rendering, I noticed that there are still places with "Polkadot or Kusama". As the page is used for both wikis we need to make sure cponditional rendering is present.
docs/build/build-guide.md
Outdated
|
||
## Development Ecosystem Overview | ||
|
||
![Path to Building a Parachain](../assets/parachain-development.png) |
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 find this figure a bit convoluted. Especially the lines linking things to the cumulus box is unclear to me. Can you explain further?
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 idea was to sort of show the relationships between various components, and how one could morph from one to another. Pallets make up your custom runtime -> Which are used by FRAME -> Which are both built on Substrate.
The Cumulus part was to also show that really, they are all concluded as a runtime no matter the path you take (parachain or solo chain).
I'll work on making t clearer, probably a top-down approach is better 👍
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.
Any updates on 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.
I will be working on it early next week - the education repo has been taking my time :)
I'll request your review when I complete the last set of changes 👍
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.
Actually, it seems a lot of that repo may be relevant here! I'll probably tag you in some of the diagrams I'm putting together over there :) Mostly to do with frame
and their relationship with Substrate core libraries, that kind of stuff
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.
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.
If something like this is good, then I can theme it
edit: themed.
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 am seeing this with a lot of delay, but the outcome is great, thanks!
Kusama, or even as a basis to form a conventional layer one solo chain. | ||
|
||
Currently, the most streamlined way of utilizing Substrate is | ||
[FRAME](https://docs.substrate.io/learn/runtime-development/#frame), which conveniently allows for a |
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.
In the future, we should try and gradually reduce links to docs.substrate.io
and instead rely more and more on our RUST-docs in the short term, and in the long term (paritytech.github.io) on the new doc portal.
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.
That'd be awesome. Right now, the only equivalent to those docs in the Rust docs is this one as far as I know 😅 https://paritytech.github.io/substrate/master/frame_support/macro.construct_runtime.html
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.
Once https://github.com/paritytech/substrate/pull/14137/files is done, we can use it here :)
Substrate chains. It consists of a development server and fluent API, which facilitates multichain | ||
interactions without compromising either performance or ease of use. </TabItem> | ||
|
||
<TabItem value="subxt"> Submit extrinsics (transactions) to a Substrate node via RPC using Rust. |
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.
👍
@filippoweb3 addressed |
Co-authored-by: Filippo <110459737+filippoweb3@users.noreply.github.com>
Co-authored-by: Filippo <110459737+filippoweb3@users.noreply.github.com>
Co-authored-by: Filippo <110459737+filippoweb3@users.noreply.github.com>
Co-authored-by: Filippo <110459737+filippoweb3@users.noreply.github.com>
Co-authored-by: Filippo <110459737+filippoweb3@users.noreply.github.com>
824f392
to
6591ec7
Compare
@kianenigma @DrW3RK @filippoweb3 I have polished and simplified this page and have a working diagram for the overall ecosystem development path. Some things to consider:
|
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.
lgtm, but I am probably not the best person to approve this PR as I still lack some knowledge about dev. Leaving final approval to Kian or Radha here.
This is very resourceful. Thank you, Bader! Let's merge this and share the readable Wiki doc to the relevant teams at Parity for feedback. |
@filippoweb3 psst, needs your approval (changes were addressed!) :) |
Creating a development "funnel" that clarifies the paths one can take in order to start developing on Polkadot. It is not meant to be a guide for everything, rather a concise series of pointers to necessary content oriented for builders.
This PR was created mainly because there has been a lack of clarity for some of those who are new to the ecosystem but wish to either simply tinker with Polkadot or dive into it at a more professional level.
Broad goals: