kujian/frontendDaily: a Chinese-language frontend link archive built on GitHub Issues

What frontendDaily actually is, and who it is for

The name suggests a tool. It is not. kujian/frontendDaily is a publication: a Chinese-language frontend blog whose daily output is published as GitHub Issues and whose back catalogue is stored as year-named folders in the repository root. The topics list on the repository reads like a newsletter's tag cloud (css, javascript, vue, jquery, news, newsletter, weekly), and the README points readers at the issue tracker as the place where the daily content appears.

The audience is narrow and clearly stated. Every resource offer in the README is gated behind a WeChat public account: reply with a keyword and you receive PDFs, mind maps, interview collections or an invitation to a group. The README describes a 500-person frontend group behind the 加群 keyword. That tells you the project assumes a reader who already uses WeChat and reads Simplified Chinese. If you do not, the value drops sharply, because the linked articles are overwhelmingly Chinese-language posts.

What it solves is discovery, not engineering. A frontend developer who wants a filtered stream of articles without assembling their own feed gets one here. The filtering is editorial and human, performed by the maintainer, and the archive is public enough that you can read it without an account.

Why the content lives in Issues and year folders

The repository layout is the mechanism. At the top level you find .github/, 2019_README.md, 2020_README.md, 2021_README.md, 2022-2023_readme.md, INTRO.md, SUMMARY.md, book.json, _book/, and folders named 2016 through 2024. There is no src/, no package.json, no build script. The primary language is listed as HTML, which is consistent with a repository that mostly stores rendered pages and index files rather than application code.

The daily stream runs through GitHub Issues instead. The README embeds an auto-generated activity block between two HTML comment markers, START_SECTION:activity and END_SECTION:activity, listing recently opened issues in kujian/frontendDaily and in sibling repositories such as kujian/githubTrending and kujian/cnas. This is the classic readme-activity pattern: a bot or scheduled job writes the block, and the marker comments let it rewrite the same region without touching the rest of the file.

The practical consequence is that the Issues tab is the feed and the folders are the archive. Two surfaces, one project. book.json and _book/ suggest the yearly material was at some point assembled with GitBook, though the README does not describe a current build step, so treat that as a leftover convention rather than a documented pipeline.

Reading the archive without cloning it

There is no install. The README gives no npm package, no CLI, no Docker image and no configuration file, so any instruction that told you to run a command would be invented. What the README does give is a set of entry points.

The daily stream is the Issues tab of the repository:

# open the daily feed in a browser
https://github.com/kujian/frontendDaily/issues

You should see a list of numbered issues, the newest at the top, each one a dated collection of links. The README's own activity block references issue numbers in the 1760s, which is a rough indicator of how long the feed has been running.

The second entry point is the yearly archive. The README links a 2019 archive file and two WeChat posts summarising 2020 and 2021, and the repository root carries folders from 2016 through 2024 plus matching README files:

# clone only if you want to grep the archive locally
git clone https://github.com/kujian/frontendDaily.git
cd frontendDaily
ls 2019_README.md 2020_README.md 2021_README.md 2022-2023_readme.md

Those four files are the index layer. The folders underneath hold the individual entries. If you only want to read, the browser path is faster; cloning pays off when you want to search across years for a topic you remember seeing.

The WeChat dependency is the real limitation

The most useful material is not in the repository. The README routes readers to a WeChat public account for the daily picks, and the resource list, the interview album, the mind maps and the group invitation all live behind that account. The repository is the shop window; WeChat is the counter.

That matters for three reasons. First, WeChat public account content is not indexed the way a website is, so you cannot link a colleague to a specific post as reliably as you can link a GitHub issue. Second, the account is a single point of failure: the README's links to mp.weixin.qq.com are long redirect URLs with session parameters, and that style of link is fragile over years. Third, the repository cannot be mirrored into a feed reader in any documented way. There is no RSS file, no JSON index, no API described in the README. If your workflow depends on consuming content programmatically, this project does not meet it.

A second limitation is language. Everything the README advertises is Chinese. An English-speaking team evaluating it for a shared reading list will find the archive hard to skim, and the interview material in particular is tied to the Chinese hiring market, with references to specific companies and their interview loops.

How it compares with daily.dev and similar aggregators

daily.dev is the obvious comparison, and the two solve the same problem from opposite directions. daily.dev is a browser extension and web platform that builds a personalised feed from a broad set of sources, with the ranking done by the platform and the interface living in your browser's new tab. frontendDaily is a hand-picked list published by one maintainer, with no personalisation and no extension to install. You get curation instead of an algorithm, and you get a Chinese-language perspective instead of a mostly English one.

The trade-off is honest on both sides. A single curator can go deep on a niche and can explain why a link matters, which an automated feed cannot. An automated feed scales, covers more sources, and does not stop when one person stops posting. If your goal is breadth across the whole ecosystem, an aggregator wins. If your goal is a short, opinionated list in Chinese that you can read in five minutes, this repository is the better fit.

Compared with a plain newsletter, the difference is the archive. Newsletters bury old issues in an inbox or a paid archive. Here the back catalogue is a public repository with year folders going back to 2016, which is the single strongest argument for this format.

Maintenance, licensing and what the README leaves out

The repository is not archived, and the last push was on 2026-08-11. That is recent enough that the project cannot be described as abandoned, but the README does not state a publishing schedule, so the cadence of the daily feed is something you have to observe rather than read about. There are no retrieved releases, which is expected for a content repository: versioning a blog does not make sense.

The licence is Apache-2.0, declared at the repository root as LICENSE. For a content repository that is an unusual choice, and it is worth being precise about what it does and does not settle. Apache-2.0 is a software licence with an explicit patent grant and a requirement to preserve notices. It covers the repository contents as distributed, but the linked articles, images and PDFs belong to their original authors, and the README's resource offers are tied to a WeChat account rather than to the licence. If you plan to republish any of the curated material, the licence on this repository is not the permission you need. That is a question for the original publishers, not a reading of LICENSE.

Upgrade cost is close to zero in the software sense, because there is nothing to upgrade. The maintenance cost that does exist is link rot: a curated archive of external URLs decays as sites move and WeChat links expire, and the README documents no link-checking step.

Editorial conclusion

Adopt frontendDaily if you read Chinese and want a low-friction way to follow frontend topics without an RSS reader or a newsletter subscription: the issues list is public and the yearly folders go back to 2016. Skip it if you need English-language coverage, an API, or a machine-readable feed, since the README documents none of those and the project is a publication rather than a library. Before relying on it, open the issues list and confirm the posting cadence still matches what you need, because the README itself does not state a schedule.

Frequently asked questions

Official sources

1. Issues
2. kujian/frontendDaily on GitHub
3. License: Apache-2.0
4. Project website
5. README