-
Notifications
You must be signed in to change notification settings - Fork 653
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
Update the AngularJS wiki instead of a standalone repo #14
Comments
The exact goal of this repository is to help everyone with the best practices. It also include some useful tools (ngmin, ng-annotate, Yeoman, etc.). The practices you've included in the AngularJS's wiki look pretty useful too. The benefit of using AngularJS's wiki is obvious - it is located in AngularJS's repository and I'm absolutely sure that AngularJS' repo is the right place for such document. Currently the best practices section in the AngularJS's wiki has 7 contributors (I'm sorry if I'm wrong) and it is not that exhaustive. This style guide has 7 contributors for the passed 20 hours. This make me believe that it might be more open and easier to find. What are the problems you see in this guide? It will be awesome if we can fix them as quick as possible. |
The official docs are not crawlable by Google and have no direct links and The wiki however is farther along by far. I discontinued my tips and tricks If you believe you have a following, then redirect that following to the I don't have time / energy to correct every peice of "best practice" P.S. If you read the best practices you would be able to answer your own
|
I think there is no need for further discussion, we don't need to repeat something like this again. P.S.: I will include link to the best practices in the AngularJS's wiki in the document. :-) |
Just sayin'
I mean, might as well help everyone with best practices: https://github.com/angular/angular.js/wiki
Not to mention I've been working on it for a while and there are a few problems with your style-guide.
The text was updated successfully, but these errors were encountered: