-
Notifications
You must be signed in to change notification settings - Fork 16
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
move lg-arc4.md content to docstrings #364
base: main
Are you sure you want to change the base?
Conversation
... | ||
|
||
``` | ||
### Mutability |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not all of the documentation on this page seems to have been replicated, e.g. this section (unless I'm missing something?)
I like the idea of moving more docs into doc strings - it's powerful for automation and maintenance and also improves intellisense. One thing I would caution though is removing conceptual documentation completely isn't a good experience since, per the UX report we did, it's important to support unknown information tasks as well as known information tasks. Completely removing the ARC-4 page and requiring people to navigate to the specific parts of it in the A-Z index won't work for that. It may well be that the conceptual docs are kept in dev portal repo though. |
This is a draft PR showing what moving existing documentation to docstrings would look like. The main idea is that all of the conceptual documentation will be hosted on the new devportal, thus making a lot of the conceptual content redundant. The goal is to make docs easier to maintain and to provide more context in docstrings where applicable.