-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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: Streamlined the new shield guide #2515
Conversation
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.
While I have some notes, I think this page really needed straightening up and this is great overall. Thanks!
As an aside, cosmetically, it'd be nice to have empty lines in some places where tags like <TabItem>
are used, e.g. one before open tag and one after close.
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.
Added some whitespace and I think resolved all the comments.
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.
LGTM, you can merge once you rebase with the encoder factoring commits.
Also, all four points in your future plans sounds good and necessary to me. Thanks again for cleaning up this page! |
a781daa
to
53152ca
Compare
Co-authored-by: Cem Aksoylar <[email protected]>
* docs: Streamlined the new shield guide --------- Co-authored-by: Cem Aksoylar <[email protected]>
* docs: Streamlined the new shield guide --------- Co-authored-by: Cem Aksoylar <[email protected]>
* docs: Streamlined the new shield guide --------- Co-authored-by: Cem Aksoylar <[email protected]>
* docs: Streamlined the new shield guide --------- Co-authored-by: Cem Aksoylar <[email protected]>
This PR builds on #2510 in an attempt to streamline our new shield guide somewhat. I do see some further improvements that can be made, but I think this version reads nicer and eases future improvements. In particular, the future improvements I'd like to see are:
I think the above steps are likely required in order to be able to write a nice "New Keyboard Board" guide in the future.