-
Notifications
You must be signed in to change notification settings - Fork 252
Initial version of the docs #2
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
Conversation
|
Thanks @Sergio0694 Let's do a light pass on this, and we can break-out larger changes or improvements as separate tasks/PRs? |
Co-authored-by: Matt Lacey <[email protected]>
Integrating a number of different suggested changes from @mrlacey that didn't have follow up questions. Addressing them individually in separate commits to be worked on. Co-authored-by: Matt Lacey <[email protected]>
|
@Sergio0694 we should also have an abridged version of the Intro in the Readme for the repository root as well as calling out samples etc... think we should do that as a separate PR or start the skeleton of that here? |
I thought the idea was to make this a quick PR to get the docs in and then make subsequent changes separately. I know I've raised dozens of comments on this already but I did feel a little bit worse every time I did so. |
|
@michael-hawker I think we should do that as a separate PR to get this one merged in, yeah 👍 @mrlacey Don't say that, those feedbacks were super useful! And we've almost addressed all of them already! 😊 |
Agree, good points. Let's merge this in now, and we can make incremental improvements as we go! Thanks! |
Docs for CommunityToolkit/WindowsCommunityToolkit#3229
NOTE: the
toc.mdfile is just a placeholder and is taken from the actual docs repo, just adding the section for the MVVM package. So all the other links are actually invalid with respect to the branch on its own (same for assets missing, etc.).