# Miden Documentation Update
Our goal is to have the best documentation in our competitive field (Aztec, Aleo, StarkNet, Fuel). We think, good documentation and tutorials are more important than hackathons or presentations.

## Target group
There are 3 types of readers we are interested in (in that order, so 1 is the most important group for us now):

1. People who want to use Polygon Miden. For now, this is mostly people who may want to play with it - but in the future could be people who want to participate in running the network.
2. People who want to develop on top of Polygon Miden - e.g., write new smart contracts (accounts, notes), build new application etc.
3. People who want to contribute to Polygon Miden - e.g., those who may be interested in making proposals to improve the protocol, or contribute to note/client development etc.

## Structure of the docs
We have some docs already published [here](https://docs.polygon.technology/miden/).

Currently, the docs in the `Miden architecture` section explain core concepts (Accounts and Notes), implementation details (`byte` sized of data structures) and specific MASM procedures (`transaction procdures`).

We aim to structure the docs more like in the [Miden VM docs](https://0xpolygonmiden.github.io/miden-vm/intro/main.html).

The final docs should

1. show high-class tutorials that explain how to use Miden and guide the user through all the new features
2. show a user documentation that explains how to develop on Miden. This is similar to the User Documentation in the Miden VM docs
3. show an architecture sections (similar to the Design section in the Miden VM docs) that explain the pros and cons of the Miden architecture without going too much into detail

This is the final strucutre of all our docs that we will have, [here](https://github.com/0xPolygonMiden/miden-docs/issues/2).

## Specific To-Dos
- Currently the best start would be to refactor the Miden architecture section and make it a better read
- The architecture section should explain the core concepts, the reasons why those were chosen, their pros and cons
- Some information in the architecture docs are implementation details, like the `transaction procedures`
- Some information is not sufficiently clear or might be even a bit outdated
- ...