[DIP 1: DIATAXIFY] Docs: Structure

[critesjosh]

This is an issue to track all of the desired changes for updating the docs. The context for the docs changes are going through the current docs and thinking about how we can improve them based on Learning Journeys.

Add issues here:

Tasks

Beta Give feedback

1. Extract how-tos from docs. Put them on the same level but in a new page (might need to make its parent a category) #110
   +0
   
2. Extract explanations from docs. Put them into concepts. Rename concepts to learn and organize them #115
   Aztec Docs +1
   
3. Extract references from docs. Put them on the same level but in a new page (might need to make its parent a category) #116
   +0
   
4. Consider adding a "Development" page to Foundational Concepts section that describes the Sandbox/CLI and links to the detailed pages
5. remove this page: https://docs.aztec.network/dev_docs/aztecjs/main
6. Create How To Test doc #111
   documentation +1
   
7. Consider trimming down the About Aztec section
8. Diataxify Aztec.nr syntax docs aztec-packages#3282
   +0
   
9. Aztec docs: Grammar consistency throughout #73
   Aztec Docs Noir Docs +2
   
10. Docs: Updated Foundational Concepts page aztec-packages#3715
    documentation +1
    
11. Docs: Update contracts/syntax/storage page aztec-packages#4157
    +0
    

Learning journey references:

• 1-pager (WIP)
• mindmap

[critesjosh]

A small piece of feedback that I'm not sure how to add to the list.

The docs talk about proving things. for smart contract devs, proving often means something different in zk land vs smart contract land. proving for Ethereum devs means revealing all of the data, not so for aztec

[critesjosh]

Also, at the top of some pages, it says "you will learn X on this page". Consider adding "if you want to learn Y go to these pages", for the case where someone lands on that page that is actually looking for a related topic. The API pages be a good place to add these

[catmcgee]

You can find the new proposed structure on Notion

[critesjosh]

@catmcgee is this work carrying on into this week's iteration?