Skip to content
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

[Tracking Issue] Docs #1456

Closed
31 of 55 tasks
iAmMichaelConnor opened this issue Aug 8, 2023 · 1 comment
Closed
31 of 55 tasks

[Tracking Issue] Docs #1456

iAmMichaelConnor opened this issue Aug 8, 2023 · 1 comment
Labels
documentation Improvements or additions to documentation tracking

Comments

@iAmMichaelConnor
Copy link
Contributor

iAmMichaelConnor commented Aug 8, 2023

Docs tracking

These tasklists list pages of the docs. If you'd like to work on a page:

  • Convert the 'draft' tasklist row into a proper GitHub issue.
  • Assign that issue to yourself.

Refer to sidebar.js for the current ordering of the pages, when they're built by docusaurus.

If you want to create new pages / split a page / or consolidate pages into one, that's probably fine - let's have a quick chat about it.

If you're not sure what should go on a page:

  • Take a look at the current content of the page. There might be a short placeholder blurb, summarising what should go there
  • If there isn't anything there, or if you still have doubts, let's chat - we might have got the suggested page titles slightly wrong.

Remember: there's a macro for injecting code from the codebase as code snippets into your docs. See docs/README.md for details.

Note: if you're writing a 'how to' guide (providing a recipe of step-by-step instructions), please consider using the TUTORIAL_TEMPLATE.md.

docs/dev-docs/getting_started

See here

Fast, and to-the-point. Instructions for getting a dev installed and using the software asap, with no friction.
Leave most detail for the more-detailed versions of these pages elsewhere in the docs.

docs/dev-docs/getting_started

  1. documentation
    rahul-kothari
  2. PhilWindle
  3. documentation
    PhilWindle
  4. documentation
    catmcgee critesjosh

docs/dev-docs/contracts/

See here

See the Solidity docs to understand why the pages have been split in this way, and for inspiration about the tone of these pages.

docs/dev-docs/contracts

  1. documentation
    LeilaWang
  2. documentation
    LeilaWang
  3. documentation
    LHerskind Maddiaa0
  4. documentation
    sirasistant
  5. Maddiaa0
  6. benesjan
  7. documentation
    spalladino
  8. documentation
    benesjan
  9. documentation
    benesjan
  10. documentation
    LHerskind
  11. rahul-kothari

docs/dev-docs/contracts/resources

See here

These pages should give opinionated examples of patterns we'd like to see.
If you can think of other patterns that you've encountered so far, please add pages :)

docs/dev-docs/contracts/resources

docs/dev-docs/dapps

See here. Lots of questions listed here, for inspiration. Should covers aztec.js, e2e test examples, and generally how to write a javascript dapp. There's a big list of suggested content at this link. You might need wish to split it into many pages.

docs/dev-docs/dapps

  1. documentation
    PhilWindle
  2. documentation
    spalladino
  3. documentation
    spalladino
  4. documentation
    spalladino
  5. spalladino
  6. spalladino
  7. spalladino
  8. spalladino
  9. spalladino

docs/dev-docs/sandbox

See here. Lots of questions listed here, for inspiration. There's a big list of suggested content at this link. You might need want to split it into many pages. Feel free to modify the page layout as you please.

docs/dev-docs/sandbox

  1. PhilWindle

docs/dev-docs/cli

See here. Lots of questions listed here, for inspiration. There's a big list of suggested content at this link. You might need want to split it into many pages. Feel free to modify the page layout as you please.

docs/dev-docs/cli

  1. documentation
    PhilWindle

docs/dev-docs/wallets

See here.

One of the key early users of the sandbox will be teams who wish to create wallet software for Aztec. We should write some beautiful explanations tailored towards this use case.
Feel free to modify the page layout as you please.

docs/dev-docs/wallets

  1. documentation
    spalladino
  2. documentation
    spalladino
  3. documentation
    spalladino

See here.

docs/dev-docs/testing

  1. documentation

TODO: tasklists for the other sections. We've only got tasklists for the dev-docs pages so far.

Foundational Concepts

@iAmMichaelConnor iAmMichaelConnor added documentation Improvements or additions to documentation tracking labels Aug 8, 2023
@iAmMichaelConnor iAmMichaelConnor modified the milestones: 🚀 Initial Aztec Sandbox Release, 📢 Initial Public Sandbox Release Aug 25, 2023
@iAmMichaelConnor
Copy link
Contributor Author

Closing this issue, in favour of devrel deciding how best to track issues for the docs, going forward. cc @critesjosh @catmcgee @rahul-kothari

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation tracking
Projects
Archived in project
Development

No branches or pull requests

1 participant