Contributing to the Angular Docs

Covers the process of submitting a PR and encourages people to participate in the angular community and repo.

Transcript

1. Contributing to the Angular Docs @kapunahelewong @kapunahele
2. https://angular.io/docs
3. Why? Community.
4. But the real reason?
5. It’s cool.
6. How I met the docs
10. My first PR.
13. Everyone has to start somewhere.
15. What I thought it might be like.
17. What it was really like.
19. Even when I did things like this in git.
21. Or this
23. People were still like this.
25. Changes to the docs
27. Checklist See CONTRIBUTING.md. Search Issues. Sign the Contributor License Agreement. Search PRs.
28. PR ideas Typos Missing commas Clarification Code formatting Small PRs are easier
29. Where are the docs exactly? What Where Guide aio/content/guide Tutorial aio/content/tutorial Example apps aio/content/examples API docs See link in doc
33. Ex: HttpInterceptor API doc
34. Basics
35. 2a. Clone your fork. 1. Fork angular/angular
36. Make your changes in your favorite editor. 2b. 3. 4. 5. 6. xxxxxxxxxxxxxxx
37. Examples of commit messages
38. Running the Angular docs locally
39. https://goo.gl/XHyk1R A gist on local setup
40. 7.
41. 8. Submit your PR.
42. After you’ve submitted your PR Labels Comments Technical Style Make changes, (squash), push back up
43. Needs to pass all the tests: Rebase, push back up
44. Big ideas File an issue first
45. Community.
47. Solid documentation Faster learning curve More highly skilled devs More great apps = = =
48. Apl-pos, a Jul’hoan village 12 km. west of Tsumkwe, Namibia.
49. We don’t code for ourselves.
50. 0.24% of the world’s population codes for the other 99.76% This is our community, too.
51. You can sit with us. (I tested it. It’s true.)