search

isobar-us / code-standards

Isobar Front-end development coding standards. Memorize them BY HEART.
https://isobar-us.github.io/code-standards/
1.34k stars 422 forks source link

A section for demos or tutorials, test cases, or other? #24

Open jaredwilli opened 12 years ago

jaredwilli commented 12 years ago

I think adding a section listing links to tutorials, and maybe other things even as well, would be a good addition. It certainly couldn't detract any value from the page at all.

This is a Standards page, but I feel like doing tutorials impacts our abilities to progress and it's "practice", to be the best you can be. See what I did there... It could be really useful too, for the more junior devs.

This isn't to say that just any 'ol link should get listed, but the more well done ones that we may want to list. Example links

Canvas: http://manuel.kiessling.net/2012/04/02/tutorial-developing-html5-canvas-games-for-facebook-with-javascript-part-1/ http://blog.safaribooksonline.com/2012/04/27/html5-games-optimizing-your-game-loop/

JavaScript: http://addyosmani.com/resources/essentialjsdesignpatterns/book/

Other Resources: http://developer-evangelism.com/handbook.php

Debugging: https://developers.google.com/chrome-developer-tools/docs/scripts-breakpoints

Ps. This definitely should get added to resources before I forget this https://wiki.mozilla.org/Engagement/Developer_Engagement/Grab_bag

rcherny commented 12 years ago

Jared, ping me at work next chance you get. We can chat about this. I'm thinking another, related repo. Think different ;-)

rcherny commented 11 years ago

Keeping this content fresh is the biggest limiter here. Still thinking about a related set of wiki pages or something.

jaredwilli commented 11 years ago

That is something I think most documentation has to deal with, so I've been learning actually in a far larger scale with what I've been working on for past couple months with Addy and Paul while contributing to the DevTools docs.

Up to date content, including correct links which point to something which is not kept up to date itself is hard to really control much. My best possible suggestion which is what I've tried to do for Devtools docs is to try and link to things which are known sources which are maintained and updated or otherwise a general rule of thumb which requires no need to be changed. There are likely many links that could be replaced with better more noteworthy references for a certain thing, or otherwise removed entirely if it's a link to some content that is outdated or could soon be out of date.

My cents on this.

rcherny commented 11 years ago

@jaredwilli I think your comment here is most appropriate for ticket #49 re: pulling all but the most solid and authoritative links out to some wiki or something more fluid.