Giters

mgechev / angularjs-style-guide

📚 Community-driven set of best practices for AngularJS application development

Home Page:https://mgechev.github.io/angularjs-style-guide/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Update the AngularJS wiki instead of a standalone repo

ProLoser opened this issue · comments

commented

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.

commented

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.

commented

The official docs are not crawlable by Google and have no direct links and
the best practices part of the docs are outdated.

The wiki however is farther along by far. I discontinued my tips and tricks
article and blogging to improve the official docs.

If you believe you have a following, then redirect that following to the
wiki and transfer anything you are able to.

I don't have time / energy to correct every peice of "best practice"
material out there, so instead I am calling upon people to put their best
foot forward and work together in a central location.

P.S.

If you read the best practices you would be able to answer your own
question.
On Oct 7, 2013 12:12 AM, "Minko Gechev" notifications@github.com wrote:

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.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-25788727
.

commented

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. :-)