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

docs: documentation redesign #1110

Open
paul-schaaf opened this issue Dec 6, 2021 · 7 comments
Open

docs: documentation redesign #1110

paul-schaaf opened this issue Dec 6, 2021 · 7 comments
Labels
documentation Improvements or additions to documentation
Projects

Comments

@paul-schaaf
Copy link
Contributor

@armaniferrante and I have been discussing a plan for anchor's new documentation. This issue is to gather feedback before we proceed.

Here's the initial plan:

  • three docs
    • the guide: this is where we explain topics (https://v3.vuejs.org/guide/introduction.html / the rust book), maintained by very small group, 1-2 people, in order to keep writing and teaching style consistent
    • the reference: =docs.rs, most up to date, maintained by everyone, if you commit sth, you update the reference
    • the cookbook: https://vuejs.org/v2/cookbook/index.html, a little bit similar to what the anchor tutorials are right now, although instead of focusing on how specific anchor features work it is more focused on showing how specific patterns independent from anchor can be implemented in anchor (e.g. how do I set up global admin settings for a program in anchor). I'd prefer the core team not to maintain this at all except maybe in the beginning and then hope anchor users contribute. This might work because contributing to the cookbook does not require you to get familiar with how anchor works under the hood, you just need to know how to use it well. might not be necessary at all if solanacookbook.com is good enough
@paul-schaaf paul-schaaf added the documentation Improvements or additions to documentation label Dec 6, 2021
@armaniferrante
Copy link
Member

One thing I'd add is that I really love when it's easy to run and play around with complete examples (this is what the current docs attempt to do). So for the first and last doc types, it'd be great to allow that either in browser or via github.

@paul-schaaf paul-schaaf added this to Done in Priorities Dec 30, 2021
@paul-schaaf paul-schaaf moved this from Done to In progress in Priorities Dec 30, 2021
@paul-schaaf
Copy link
Contributor Author

paul-schaaf commented Dec 31, 2021

Reference Checklist:

@Necmttn
Copy link
Contributor

Necmttn commented Jan 3, 2022

Wanna help! already have one open PR for ts client documentation.

@paul-schaaf
Copy link
Contributor Author

hey @Necmttn sorry for the late reply. Are you still interested in writing ts documentation? One thing that would be really helpful is a section in the book that shows how all the different rust types are mapped to ts types. e.g. u64 -> BN

@ashpoolin
Copy link

Hey @paul-schaaf, Noah and I putting together a PR to add events to the docs:

#2008

Let us know if there's another section you think is a high priority to write next. Thanks, Ash

@armaniferrante
Copy link
Member

Will look at it @ashpoolin!

@ggold7046
Copy link

Hi , is this issue still open ? I would love to join you guys.

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
Projects
Priorities
In progress
Development

No branches or pull requests

5 participants