Adds Learn segment with 4 main sections

[loonggamma]

The Learn section is an improvement of Massa's Architecture section.

Planned sections in order:

1. Basic concepts (previous Introduction), which needs improvements in content. I instructed what needs to be done..
2. Node Architecture (previous Architecture) which needs validation as I shortened some content where I could.
3. Operation lifecycle (as it was, no need to fix it)
4. Consensus quality initiatives - a new section for which I planned to include:

• Endorsements (needs core validation as I shortened some parts and also needs their check since they made some changes to endorsements object)
• Slashing (needs a full write up)
• Node banning (needs a full write up). The idea with this new section is to unify all (dis)incentives in our consensus in one place where you can learn how we maximize the quality of our network.

---

All needed changes/needed content or checks I showed in Admonition :::danger

To do:

• Validate my summaries and planned structure;
• Add all diagrams and tables as indicated in the code;
• Add equations using Katex for parts of the code in ``
• Fill all links that currently don't exist.
• Improve content specified in Admonitions -> danger mode -> done, creating separate issues to be tackled by Core team

[loonggamma]

@gregLibert:

Content of Learn part is ready to be filled by intern for:

• links
• equations with Katex
• Diagrams and images as marked with Admonition :::danger
• reorganize the sidebar in case we go with 1 concept per page, like Block, Operation, etc.

Note: I created sections that need write up by Core team and marked with - to do, so they can navigate easier. Also lines have been broken for easier navigation in the docu.

[gregLibert]

@gregLibert:

Content of Learn part is ready to be filled by intern for:

• links
• equations with Katex
• Diagrams and images as marked with Admonition :::danger
• reorganize the sidebar in case we go with 1 concept per page, like Block, Operation, etc.

Note: I created sections that need write up by Core team and marked with - to do, so they can navigate easier. Also lines have been broken for easier navigation in the docu.

@windushka Can you please help us here ? feel free to poing @longgamma-massa or myself if you need some help!

[loonggamma]

@gregLibert applied changes to content instructed by Aurelien.

[gregLibert]

@longgamma-massa can I merge this branch ?

[loonggamma]

@longgamma-massa can I merge this branch ?

@gregLibert @windushka

The links for JSON RPC and GRPC are incorrect in the 'architecture' file -> 'API module' section. They lead to providers list instead of to pages where JSON RPC and GRPC documentation will be hosted, not the list of providers.

They rest is good to be merged (note: there are still subsections in text marked as 'to do' for Core's further work (issues are crearted).