background preloader

Dypsilon/frontend-dev-bookmarks: Manually curated collection of resources for frontend web developers.

Dypsilon/frontend-dev-bookmarks: Manually curated collection of resources for frontend web developers.
Related:  GraphismeA classer

Front-End Checklist | Front-End-Checklist A Baseline for Front-End Developers 12 Apr 2012 edit I wrote a README the other day for a project that I'm hoping other developers will look at and learn from, and as I was writing it, I realized that it was the sort of thing that might have intimidated the hell out of me a couple of years ago, what with its casual mentions of Node, npm, Homebrew, git, tests, and development and production builds. Once upon a time, editing files, testing them locally (as best as we could, anyway), and then FTPing them to the server was the essential workflow of a front-end dev. Something has changed in the last couple of years. Whatever it is, I think we're seeing the emphasis shift from valuing trivia to valuing tools. Here are a few things that I want to start expecting people to be familiar with, along with some resources you can use if you feel like you need to get up to speed. JavaScript This might go without saying, but simply knowing a JavaScript library isn't sufficient any more. Git (and a Github account) Skeptical of AMD? Testing

10 Web Application Frameworks for Node.js Yes, this is the 2nd edition to my list of Node.js frameworks, the first one was where I had put together a list of seven minimal Node.js frameworks, which later turned into one of my most visited, shared and admired posts on this blog. If you were a part of the success, thank you and hopefully we can make this one just as good. I have since received a ton of emails, comments and social media queries with suggestions, and questions as to what else is out there. I’m gathering these up by paying attention to their usage / popularity on open-source websites like GitHub and Bitbucket, while also keeping an eye on sites like Hacker News, and Reddit. Hello World! Remember the silly ‘Hello World!’ You can either watch it to refresh your memory, introduce yourself to WebStorm (IDE), perhaps even begin learning about Node.js and the basics of it, or you can simply move on. Is Node.js Good or Bad? What do you think? 12 Web Application Frameworks for Node.js begin UPDATE 20/03/2014 Primus Geddy Keystone

Draw.Chat - Collaborative Drawing Board Online cunning ramblings in codecraft – Pseudo-random Contributions to the Global Mind-meld 12 Best JavaScript Libraries for February 2014 | Design Geekz JavaScript (JS) is an interpreted computer programming language. It was originally implemented as part of web browsers so that client-side scripts could interact with the user,control the browser, communicate asynchronously, and alter the document content that was displayed. In this article, We have collected 12 of the latest of these JavaScript libraries for February 2014 to help you enhance your website related tasks and keep your website a step ahead of the competition. We hope you will find a few of the JavaScript libraries below beneficial to your web related needs. Enjoy !! 1. CutJS is a minimal JavaScript library for composing high-performance, dynamic and intractable 2D HTML5 graphics. 2. Sticker.js is a lightweight javaScript library that allows you to create a Sticker Effect. 3. Fattable is a javascript Library to create table with infinite scroll, with infinite number of rows and number of columns. 4. fn.js 5. 6. 7. 8. 9. 10. 11. 12.

Guide to building layouts with CSS Grid Representational State Transfer Un article de Wikipédia, l'encyclopédie libre. REST (representational state transfer) est un style d'architecture pour les systèmes hypermédia distribués, créé par Roy Fielding en 2000 dans le chapitre 5 de sa thèse de doctorat[1]. Il trouve notamment des applications dans le World Wide Web. Contraintes[modifier | modifier le code] Une architecture REST doit respecter les contraintes suivantes : Client-serveur : les responsabilités sont séparées entre le client et le serveur. Description[modifier | modifier le code] Assimilation à un protocole ou un format[modifier | modifier le code] Ce style architectural s'applique tout autant à la réalisation d'applications pour un utilisateur humain qu'à la réalisation d'architectures orientées services destinées à la communication entre machines. RPC ainsi que SOAP ne sont pas des styles d'architecture mais des protocoles. Avantages de REST[modifier | modifier le code] Inconvénients de REST[modifier | modifier le code] ↑ (fr) Thèse de Roy T.