chore: docs restructure

[catmcgee]

• Removed some things from the sidebar that were empty/WIP
• Filled out 'how to participate' and 'visibility' sections
• Changed around structure to make it easier to follow
• use #include_code macro to pull in code from tests for getting started page
• closes Review the monorepo README #1905

Checklist:

Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

• If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
• I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
• Every change is related to the PR description.
• I have linked this pull request to relevant issues (if any exist).

[critesjosh]

I will start reviewing this, thanks Cat!

cc @iAmMichaelConnor so you can flag anything that might be concerning

[iAmMichaelConnor]

There's another 'getting started' guide somewhere that mentions port conflicts. We should mention that here too. If they get errors about port conflicts, when running this curl command, they should check whether those ports are already in use (insert the commands which would enable someone to check conflicting ports for 8080 and 8545).
To specify different ports, they'd need to edit the docker-compose file which got saved in .aztec/docker-compose.yml: nano .aztec/docker-compose.yml then change PORTS: 8080:8080 to PORTS: <other port>:8080 (and same for 8545 if there's a conflict at that port too). (I might have got the docker compose syntax wrong - I'm basing this off memory).

(As an alternative to modifying the docker-compose.yml, a user might be able to specify an env file (from memory), with overwrites to the ports)

Then, when doing CLI commands, they'd need to specify --rpc-url=<other port> with each cli command.

[iAmMichaelConnor]

Also, if they re-run the curl command, it will overwrite their custom changes to the port number in the docker-compose.yml file. (So the env file approach might be better)

[iAmMichaelConnor]

Can we open a new issue to change the port from 8080 to 4273 (because it looks like AZTE(c)) and because 8080 is used by everything (especially the mainframe!)

[critesjosh]

I am testing out editing the docker-comose.yml file. It looks like its <other port>:8080, but when it starts up it still prints sandbox Aztec Sandbox JSON-RPC Server listening on port 8080 in the terminal even when it's been changed.

I'll update the quickstart page with this note.

[critesjosh]

created an issue here: #2381

I likely wont have time to add this to the docs in the next couple days, but can do later.

[iAmMichaelConnor]

but when it starts up it still prints sandbox Aztec Sandbox JSON-RPC Server listening on port 8080

Ah, yeah that'll be because from the sandbox's perspective, it's still communicating via port 8080 (regardless of which port you forward from your local machine)

[critesjosh]

thanks for starting this @catmcgee! I am going to merge these changes and we can make additional edits if necessary.

[signorecello]

@critesjosh I'm late to the party but I wonder if this is being deployed to netlify? Would be great to have a preview for docs changes

[critesjosh]

Yes it is. The problem is that previews will be created for every PR, which is irrelevant for most PRs and its noisy. That's why I turned it off. You can preview locally.