-
Notifications
You must be signed in to change notification settings - Fork 237
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
Standardize how we display terminal/bash code blocks #1190
Comments
Happy to jump in and help with PRs that remove |
@Akirtovskis I would certainly love the assistance - I want to just put it to our dev team to make sure this is how we want to standardize, once we've sorted that out I can provide a resource list |
@Akirtovskis After internal discussion and discussion with the community, we've settled on not including the $ stx balance SP2JM9EMVHHRHWHW82CD9XQMTYTM8BG2RWG58WQVB
{
"balance": "18588980982",
"locked": "0",
"unlock_height": 0,
"nonce": 1609
} In the above case it would be acceptable to leave as is, or as a best practice it would be preferred to split the example command and the output with some expository text between them. As far as doc updates go, this repo would be the primary target, but we would appreciate additional PRs on READMEs in any repo in the |
@pgray-hiro I am definitely up for doing this! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed. Please reopen if needed. |
We have prior art where we've typically used a code block like this to show terminal or bash commands:
However,
Akirtovskis
mentioned in stacks-network/stacks-blockchain-docker#39 that it would make things easier to remove the$
from terminal/bash, like this:Personally, I agree with this approach - the only reason I had added the
$
is because of prior docs/readme's that we've published where the$
exists.To keep this issue easily scoped, we should go through existing docs here and remove the
$
or any other shell/terminal identifier (%
is another example).Later, it would be nice to work on a style-guide that we use here with the goal of standardizing how we create docs with the goal of making them easy and accessible. ( @pgray-hiro )
The text was updated successfully, but these errors were encountered: