spellbook-of-modern-webdev

• This document originated from a bunch of most commonly used links and learning resources I sent to every new web developer on our full-stack web development team.
• What I'm doing in this document now is trying to provide the complete view angle of modern web (app or page) development ruled by JavaScript, reflect technological advance and help developers to acquire APIs, libraries, tools, services, best practices and learning resource which are not outdated and most commonly used.
• I hope this document can help one developer to have more power to do much more and much better, just like a spellbook does in fantasy worlds.
• The JS/web technology is like an ocean of stuff you don’t know. Simply collecting more stuff or composing dozens of "awesome lists" into a single one will only exacerbate the Javascript Fatigue. So this document must stay lean and focus on the most frequent problems and the most commonly used stuff.
• So for each problem domain and each technology, I try my best to pick only one or a few links.
• Which link belongs to "not outdated and most commonly used stuff" is not only decided by clear trends, empirical observation, and working experience, also by public data and web scraping scripts.
• The npm package statistics (like download count) are given more weight than Github repo statistics (like starring data) because npm statistics can better reflect the actual usage and popularity.
• Prefer fine-grained classifications and deep hierarchies over featureless descriptions and distractive comments.
• Ideally, each line is a unique category. The " / " symbol between the links means they are replaceable. The ", " symbol between the links means they are complementary.
• I wish this document could be closer to a kind of knowledge graph or skill tree than a list or a collection.
• It currently contains 2000+ links (projects, tools, plugins, services, articles, books, sites, etc.)
• Feel free to submit the missing or better links in your opinion. Also, please provide the reason.
• Why not add a Europe (or other regions) section? Why not add your project? Why so many React-based projects? Why not Angular/Vue.js/XXX?

Understanding Modern Web Development

• In English: coming soon...
• In Chinese: slides @ JSConf CN 2017

---

Table of Contents

• Platforms and Languages
  • Open Web Platform
    • Learning, Reference, Visual Tools
    • Performance, Security, Semantics / SEO / Accessibility
  • HTML5 / Web APIs
    • HTML/DOM, Appearance, Interaction, Access, Network, Media, Graphics, Computing...
  • CSS Features
    • RWD, Layout, Typography, Text, Animation, Effects...
  • Modern CSS / Next-Gen CSS
    • CSS Module, PostCSS, CSS in JS
    • Best Practices (Skeleton, Methodology, Code Style...)
    • Know More about Web Design / UI Design / UX Design (RWD, Atomic Design, Motion Design, Grid System, Typography, Style Guide...)
  • Modern JS / Next-Gen JS
    • ES6+ Features, Intro to ES6+, Re-intro to JS, Important Proposals, Functional Programming, FRP, Static Typing, Code Style...
  • WebAssembly
    • Concepts, Features, Rust, ...
  • Node.js
    • Intro, Workshop, Best Practices...
  • Platform Compatibility and Proposal Status
    • Platform Status / Releases / Updates, ECMAScript Compatibility
    • Proposal Status (W3C WG, WICG, WHATWG, ECMA TC39, Node.js CTC)
    • JS Engine (V8, JSC, Chakra), Web/JS Runtime (Electron, Cordova, React Native...), Device...
  • Cross-browser / Polyfill Libraries
    • Appearance, Interaction, Access, Network, Performance, Offline, Media...
  • npm Ecosystem
    • Finding Packages (Search, Stats, Rank)
    • Dependency Management / Release / Maintenance (npm, yarn, lerna, ncp...)
    • Convention (Open Source, SemVer, package.json, Small modules, Isomorphic JS / Universal JS...)
  • Universal Utility Libraries

A Subset as a Learning Path

1. Open Web Platform
2. HTML5 / Web APIs
3. CSS Features
4. Modern CSS / Next-Gen CSS
5. Modern JS / Next-Gen JS
6. Platform Compatibility and Proposal Status
7. Network
8. Node.js
9. npm Ecosystem
10. Command-line Environment (Mac)
11. IDE / Editors
12. GUI Framework
13. Microservices / API Services (Node.js)
14. Testing

A Subset for Finding Libraries

• Cross-browser / Polyfill Libraries
• Hybrid Libraries
• GUI Framework
• UI Toolkits
• Standalone UI Components
• UX Libraries
• Graphic Libraries
• Universal Utility Libraries
• Microservices / API Services (Node.js)
• Server-side Libraries (Node.js)
• Command-line Libraries (Node.js)

A Subset for Architecture and Infrastructure

• GUI Framework
• Toolchain
• Workflow
• Microservices / API Services (Node.js)
• Server-side Best Practices
• Cloud Services (Global) / Cloud Services (China)
• Documentation

---

Platforms and Languages

Open Web Platform

• Learning
  • What is the Internet, How does the Internet work
    • HTTP - see Server Side > Network
  • Evolution of the Web
    • Timeline of web browsers
    • Dive Into HTML5 - A Quite Biased History of HTML5
    • [20 Things