# The frontendDaily front page is a generated issue feed spanning three repositories > frontendDaily is a Chinese front end article archive kept as one directory per year, paired with a WeChat public account that republishes selected pieces. The front page's daily section is an auto-generated block of recently opened issues, and one of those issues lives in a different repository. **kujian/frontendDaily** — 前端开发博客，分享互联网最精彩的前端技术，欢迎关注我微信公众号：前端开发博客，回复 1024，领取前端进阶资料包，回复 加群，与大神一起交流学习。 - Repository: https://github.com/kujian/frontendDaily - Website: https://qdkfweb.cn - Stars: 2,385 · Forks: 193 - Language: HTML - License: Apache-2.0 - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/kujian-frontenddaily ## The daily section is a generated block of issues from three repositories The link labelled with the Chinese name for a daily report does not point at a file. It points at the repository's issue tracker, and the block under it is machine written: it sits between `` and `` comment markers, which is the convention for a section that a bot rewrites on each push. Its five entries are the most recently opened issues, and they do not all belong to this repository. Two are in frontendDaily, numbered 1769 and 1767. Two are in a sibling repository, kujian/githubTrending, numbered 2911 and 2910. The first entry belongs to a third one, kujian/cnas, issue 1. So the front page of this repository doubles as an activity feed for work happening elsewhere, which is why the issue numbers jump around and why the newest number on the page is not this project's own. ## The archive stops at 2024 while pushes keep landing The content is organised as one directory per year, and the run of directories is visible: 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023 and 2024. Alongside them sit the index files, `2019_README.md`, `2020_README.md`, `2021_README.md` and a single `2022-2023_readme.md` that covers two years at once. The 2024 directory has no matching readme file in the root listing, so the newest year of content is present as a directory without the kind of index that the three preceding years got. The last push to the repository is dated 2026-08-11 and there are no releases at all. Meanwhile the page describes a different rhythm: articles are picked each day and posted to a WeChat public account, and the group invitation says the material is updated daily. The archive in the repository and the daily claim are two separate clocks, and only one of them has a date attached to it. ## A generated GitBook build sits in the repository next to its sources Four entries at the root describe a book rather than a collection of posts. `INTRO.md` and `SUMMARY.md` are the two files a GitBook project is built from, `book.json` is its configuration, and `_book/` is the output directory, which holds the rendered site. Committing `_book/` means the repository carries both the source and the built result, so every change to a post is a change to two trees. That has a practical effect for anyone reading the repository rather than the site: the generated pages are the ones a search engine or a link preview will find, and they can lag the markdown they were generated from if a pull request updates one and not the other. There is no build step described for the book anywhere on the page, and no package manifest in the root listing, so the published site is produced by a process the repository does not describe. ## The interview links use http while the archive links use https Two link conventions sit on the same page. The two year summaries for 2020 and 2021 are https links to mp.weixin.qq.com. Every entry in the interview section below them is an http link to the same host, each one carrying a long query string with a business identifier, a message identifier, an index, a signature and a checksum. So the archive links are protected by transport security and the article links are not, which means a reader following one of the interview entries is sent over an unencrypted connection to a host that serves the same content over https elsewhere on the page. The interview list also carries at least 25 numbered entries before it ends, and each one is a bare title with a link and no date, no author and no word count. ## The numbers live in the titles, with nothing behind them The interview section is where the project's claims concentrate, and every one of them sits in a link title. The visible entries promise 170 or more DingTalk frontend knowledge points, the 150 most common leetcode frontend questions in an easy and a hard part, 66 frontend algorithm questions with approach analysis, 60 classic frontend questions with answers, 38 questions untangling what `this` points at in JavaScript, 24 answers on the difference between A and B, 21 performance optimisation questions, 10 tricky JavaScript snippets used in interviews, and 5 commonly asked Vue 3 advantages. One title goes further and claims the single article is enough because the writer got offers from Alibaba and ByteDance with it. None of that is verifiable from the repository. There is no author next to any entry, no publication date on the individual links, and no way to tell from the page whether a question set has been updated since it was written. ## Eight reply keywords stand between the page and its resources None of the material is in the repository. The page points at a WeChat public account and lists what to send it. Replying 小抄 gets PDF cheat sheets on Vue, JavaScript and WebComponent. Vue脑图 gets Vue mind maps and 思维图 gets JavaScript mind maps. 简历 gets advice on writing a resume and 简历模板 gets a selection of templates. 加群 enters a 500 person frontend group. 电子书 downloads a collection of ebooks covering interviews, Vue practice projects, CSS and JavaScript. 知识点 gets a high resolution JavaScript knowledge map. The repository description adds one more key, 1024, for an advanced materials pack. Read as a distribution design, the archive is the free sample and the account is the delivery mechanism, which means nothing linked from the front page can be checked, versioned or mirrored from here. ## Joining the group asks you to leave a note on GitHub The WeChat group section does not give a link to join. It says that if you leave a note on GitHub you will be pulled into the frontend development sharing group, updated daily. Membership is manual, which makes it a private channel rather than a published one, and it means the daily material that the group is described as carrying has no counterpart in the repository. The archive links show how the medium has shifted over the project's life. The 2019 archive is a file in the repository, `2019_README.md`, so that year is browsable by anyone. The 2020 and 2021 year summaries are WeChat article links, so those years need the account and a working connection to reach. The per year directories underneath them exist for every year from 2016 onward regardless. ## Conclusion frontendDaily suits someone browsing a back catalogue of Chinese front end material, particularly Vue, JavaScript and interview question sets, and willing to read titles rather than evaluate sources. Before treating it as a reference, notice what the page does not contain: no dates on individual entries, no authorship, and no way to check the numbers that appear in the titles. The resources themselves are not in the repository, they sit behind reply keywords on a WeChat account, and the newest dated content directory is 2024 while the last push is later than that. It is an archive and a funnel, not a maintained documentation set. ## FAQ ### What is kujian/frontendDaily? It is a Chinese front end article archive kept as one directory per year from 2016 through 2024, published under the Apache-2.0 license, paired with a WeChat public account that republishes selected articles. Its daily section is the repository issue tracker rather than a file. ### How do I browse the frontendDaily archive? Read the year directories and the index files at the root, which are 2019_README.md, 2020_README.md, 2021_README.md and a combined 2022-2023_readme.md, with INTRO.md and SUMMARY.md describing the book. A rendered GitBook build is committed in _book/ and configured by book.json, so nothing needs to be installed to read it. ### Where are the frontendDaily resources? They are not in the repository. They are delivered by reply keyword on the WeChat public account: 小抄 for Vue, JavaScript and WebComponent cheat sheets, Vue脑图 and 思维图 for mind maps, 简历 and 简历模板 for resume material, 加群 for a 500 person group, 电子书 for ebooks, and 知识点 for a JavaScript knowledge map. ### How current is the frontendDaily repository? The last push is dated 2026-08-11 and there are no releases. The newest dated content directory in the tree is 2024, and there is no 2024 readme file alongside it. The page describes articles being selected every day for the public account, which is a separate stream from the archive. ### What does the daily section of frontendDaily show? It shows a generated block of recently opened issues between comment markers, and those issues come from three repositories: two in frontendDaily, two in kujian/githubTrending and one in kujian/cnas. That is why the issue numbers on the front page are not sequential for this project. ## Sources - [Issues](https://github.com/kujian/frontendDaily/issues) - [kujian/frontendDaily on GitHub](https://github.com/kujian/frontendDaily) - [License: Apache-2.0](https://github.com/kujian/frontendDaily/blob/master/LICENSE) - [Project website](https://qdkfweb.cn) - [README](https://github.com/kujian/frontendDaily/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kujian-frontenddaily