Frontend Dev Bookmarks: a hand-curated link directory split into category files, last pushed in May 2024
GitHub describes it as Manually curated collection of resources for frontend web developers.. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- dypsilon/frontend-dev-bookmarks is a manually curated awesome list of frontend resources, organised into Markdown files by topic and mirrored in one gigantic single page. It is a useful map of the field's vocabulary, but its last push was on 21 May 2024, no license file sits at the top level, and links need checking before you rely on them.
- Who is it for?
- Frontend Dev Bookmarks suits developers who want a topic map of frontend web development, from typography and printers to service workers and functional reactive programming, and who will verify each link before using it. It does not suit anyone who needs a currently maintained list, since the last push was 21 May 2024, or anyone who plans to republish the entries, since no license file appears at the top level.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Probably not. The repository last received commits 30 months ago, on May 21, 2024.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- dypsilon/frontend-dev-bookmarks47,782 ★ · +406
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| dypsilon/frontend-dev-bookmarks | 47.4k | 47.8k |
406 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One list, published twice: category files and a single gigantic page
The repository presents the same bookmarks in two shapes. The default view is browseable: README.md acts as a table of contents, and each topic links to its own small Markdown file, such as appearance/typography.md or compatibility/e-mail.md. The second shape is TOTALLY-GIGANTIC-FILE.md, which puts every single resource on one page. The two layouts serve different habits. The category files are easier to read on GitHub and load quickly, which helps when you already know the area you want. The gigantic file is the one to open when you want to search across everything at once with your browser's find function, because there is no search index, tag system or website search inside the repository itself. The cost of the split is that a link you see in one category file and a link on the gigantic page are two copies, so if you report a broken entry, say which file you found it in.
The taxonomy is organised by discipline, not by framework
The front page groups resources under broad headings, each with a one-line definition. Appearance covers the outward or visible aspect of a website and splits into Animation, Typography and Visualization. Architecture covers the high level structure of frontend code. Compatibility covers devices and rendering software. Ecosystem covers developers, companies, organizations and news sources. Languages, Protocols, Browser APIs covers CSS, the DOM, HTML, HTTP, JavaScript, JSON, SVG and Service Workers. The top-level folders add user-interface-components/ and workflow/, plus a separate animation/ folder beside appearance/. The practical consequence of this structure is that you navigate by concept. Someone looking for help with a specific library has to think about which discipline it belongs to first: a charting library sits under Visualization, an accessibility checker under Web Accessibility. That makes the list good for learning the shape of the field and slower for answering a narrow tool question.
Architecture pages group links by programming paradigm
The Architecture category is where the list is most opinionated about how frontend developers should think. It has six pages. Algorithms covers self-contained step-by-step operations for calculation, data processing and automated reasoning. Design Patterns covers best practices for common problems in application design. Designs collects ready to use and well documented structures and frameworks for frontend development. Event-Driven Programming covers programs whose flow is set by events such as user actions or messages from other threads. Functional Programming covers computation as the evaluation of mathematical functions, avoiding changing state and mutable data. Functional Reactive Programming (FRP) covers asynchronous dataflow built from functional programming blocks. Frameworks live under Designs rather than in a category of their own. If you came looking for a framework shortlist, that is the page to open; the paradigm pages are reading material for the ideas behind those frameworks.
Compatibility reaches past browsers to e-mail, keyboards and printers
The Compatibility category defines its scope as making a product work with different input and output devices and rendering software, including printers, email, mobile devices and different browsers. Its seven pages follow that definition closely. Cross Browser covers sites and scripts that work where features exist and degrade gracefully where they are missing. E-Mail covers preparing HTML based electronic mail. Keyboard covers working with keyboard input in a web browser. Mobile covers sites optimised for smartphones and tablets. Printers covers manipulating printer output through CSS. Responsive Web Design covers layouts that change with the size and capabilities of the device. Web Accessibility covers making the web perceivable, understandable, navigable and usable by people with disabilities. Pages like Printers and E-Mail are topics that general frontend lists tend to skip, and they are the reason to keep this one bookmarked even when you use newer lists for frameworks.
The last push was 21 May 2024, though the front page promises ongoing updates
The README calls the current version the one that receives ongoing updates. The repository's history does not match that sentence today. The repository is not archived, but its last push was on 21 May 2024, so the master branch has gone well over a year without changes. For a link directory that matters more than it would for a library. Resources move, sites close and recommendations age, and nothing in a static Markdown list checks whether a link still resolves. The consequence for a reader is that every entry needs a quick sanity check before you build on it: open the link, look at the date on the page, and confirm that the project or article still exists. Treat the list as a starting map rather than a current recommendation, and expect some category files to point at resources that have since been replaced.
The v.1.0 tag keeps the 2015 list, outdated links included
The repository has a single release, tagged v.1.0 and titled Version of 2015, published on 21 May 2016. It preserves the original bookmarks before the reorganisation into category files. The front page points readers who want the good old bookmarks to that tag, and in the same breath warns that the old version has many outdated links. That warning is worth taking literally. The 2015 snapshot is useful as a historical record of what frontend developers were reading at the time, and for finding an article you remember from that period. It is a poor source for choosing tools today, since it predates the current version by years and the current version itself has not been pushed since May 2024. Anyone linking to this repository from their own documentation should link to master, not to the tag, unless the historical snapshot is the point.
No license file sits at the top of the repository
GitHub does not detect a license for the repository, and the top-level entries are README.md, TOTALLY-GIGANTIC-FILE.md, about.md, contributing.md and the category folders, with no LICENSE file among them. The list carries the awesome badge from sindresorhus/awesome, but that badge is a listing mark, not a grant of rights. The consequence is specific: reading and bookmarking the list is fine, while copying its category files or descriptions into your own site, newsletter or derived list has no stated terms behind it. If you want to build on the curation, ask the maintainer first through the Gitter room linked from the front page, or keep to linking rather than copying. Contributors adding resources should read contributing.md before opening a pull request, since it sets how new entries are expected to be added.
Ecosystem pages track people, news and podcasts
The Ecosystem category is the part of the list about who and where rather than what. Communities Around Projects collects plugins, libraries and tutorials that grow up around popular open source projects. News lists websites and newsletters with daily and weekly frontend news. Notable Community Members names engineers, evangelists, architects and other well known people in the field. Organizations covers commercial companies and nonprofits around web development. Podcasts covers episodic audio and video series. These entries describe people and publications rather than specifications, so they are the ones most exposed to a list that stopped being pushed in May 2024. Before subscribing to a newsletter or podcast from this page, confirm it is still publishing. The project also links a site at frontend.directory and a Twitter account, @FrontendDir, from its front page.
Editorial conclusion
Frontend Dev Bookmarks suits developers who want a topic map of frontend web development, from typography and printers to service workers and functional reactive programming, and who will verify each link before using it. It does not suit anyone who needs a currently maintained list, since the last push was 21 May 2024, or anyone who plans to republish the entries, since no license file appears at the top level. Check the date of a category file's last change and ask the maintainer about reuse terms first.
Frequently asked questions
Where can I see every Frontend Dev Bookmarks link on one page?
Open TOTALLY-GIGANTIC-FILE.md in the repository. It contains every resource on a single page, while README.md links to smaller category files.
Is Frontend Dev Bookmarks still being updated?
The repository is not archived, but its last push was on 21 May 2024. Check each link before relying on it.
What is the v.1.0 tag in Frontend Dev Bookmarks?
v.1.0 is the Version of 2015 release, published on 21 May 2016, which keeps the old bookmarks. The project warns that this old version has many outdated links.
What license does Frontend Dev Bookmarks use?
GitHub does not detect a license, and no LICENSE file appears at the top level of the repository. Reuse terms for copying the list are not stated there.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/dypsilon-frontend-dev-bookmarks)Star history chart for your README
[](https://hysenlabs.com/projects/dypsilon-frontend-dev-bookmarks)Was this useful?