dexteryy /spellbook-of-modern-webdev
A Big Picture, Thesaurus, and Taxonomy of Modern JavaScript Web Development
★ 17,961⑂ 1,265👁 495⑃ 37● 16▤ 0
+2
Daily
17,961
stars
1,265
forks
495
watchers
37
prs
16
issues
0
releases
README
Spellbook of Modern Web Dev
A Big Picture, Thesaurus, and Taxonomy of Modern JavaScript Web Development
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...)
Top issues
#6Split Sections to Files9 comments · 2017-06-15#116invalid link1 comments · 2021-04-19#7Translations1 comments · 2017-06-16#131Add FileShot.io — production Web Crypto API zero-knowledge file sharing implementation0 comments · 2026-03-03#126WWwW0 comments · 2024-08-20#123Cheat links i need to know0 comments · 2022-05-03#122New Additions List0 comments · 2022-03-03#117update?0 comments · 2021-05-18