wangtunan/blog: a Chinese-language study notes site built with VuePress

What this repository actually is

The README opens with a line that sets the scope precisely: the project records a personal blog and, in the author's phrasing, documents a path of growth. There is no product claim, no installable package and no API. The repository is a content site. Its primary language is listed as Shell, which in practice means the build and deployment scripts around the markdown, not that the notes themselves are shell material. The topics attached to the repository (agent, leetcode, llm, python, rag, scss, typescript, vue) map directly onto the README's table of contents, so the tags describe the subject matter of the articles rather than the technology stack of a library.

The intended audience is therefore a reader, not an integrator. Someone preparing a frontend interview, revising Vue's reactivity implementation, or starting with retrieval-augmented generation in Chinese would find the structure useful. A team looking for a documentation framework, a component library or a starter template will not find one here. The README even asks readers to star the repository or leave a tip if they think the writing is decent, which is the clearest statement of what kind of project this is.

The table of contents is the architecture

There is no architecture document in the supplied material, so the only visible structure is the README's link list. It is organised into named groups: LLM, Python, interview preparation, frontend book notes, Vue source analysis, algorithms, bundlers, TypeScript, CSS preprocessors, automated testing and VuePress itself. Each entry is a single link to a page under wangtunan.github.io/blog, with paths that reveal the folder layout, for example /rag/base/, /agent/introduction/, /vueAnalysis/introduction/ and /vueNextAnalysis/introduction/.

That path pattern tells you two things. First, Vue 2 and Vue 3 analysis live in separate trees, so the two are treated as distinct bodies of work rather than one continuous narrative. Second, most sections have an introduction page, which suggests each topic is written as a sequence rather than a single long article. The bundler section splits Webpack 4, Rollup and Vite into three separate pages, which is a deliberate choice to keep them parallel instead of comparative. What the README does not show is any navigation config, sidebar definition or theme file, so the mechanics of how those pages are assembled into a site cannot be confirmed from this material.

VuePress is named, but not configured in the README

VuePress appears twice: once as a topic tag and once as a section in the table of contents pointing at /vuepress/. That is consistent with the site being generated by VuePress, and the URL shape (clean paths with trailing slashes under a project subdirectory) matches the default output of that generator. The homepage is listed as none, which is slightly misleading given that the README itself gives the published address, https://wangtunan.github.io/blog/.

Here the documentation is thin in a way worth stating plainly. The README gives no install command, no build script, no config key and no deployment instructions. There is no mention of package.json, no .vuepress/config.js reference, no npm run docs:dev or equivalent. If you wanted to fork this and rebuild it locally, the README would not tell you how. You would have to read the repository's files, which are outside the material available here. The Gitee mirror is explicitly marked as abandoned, so the GitHub Pages address is the only live target the README endorses.

The LLM and RAG sections are the part that dates fastest

Two of the newest topics, RAG fundamentals and agent fundamentals, are also the ones most exposed to drift. Retrieval-augmented generation practice changed quickly through 2024 and 2025: chunking strategies, embedding model choices and evaluation approaches have all moved. A notes site written by one person has no mechanism to flag a page as stale. The README carries no last-updated column, no version note per article and no changelog.

The repository's last push is dated 2026-03-13, which indicates activity, but a push date says nothing about which pages changed. If you are reading the RAG or agent pages for current practice, treat them as a starting point and verify the specifics elsewhere. By contrast, the Vue 2 source analysis and the JavaScript book notes are anchored to fixed texts and fixed framework versions, so they age far more slowly. That split is the most useful thing to know before you invest time in the site: the algorithm, bundler and source-code pages are stable, the LLM pages are not.

No releases, no stated licence, no upgrade path

The material shows no releases retrieved, and the licence field is unknown. For a content repository that matters less than it would for a library, but it is not nothing. Without a stated licence, the terms under which you may copy, translate or republish the articles are unclear, and the README's request for stars and donations does not settle that question. Anyone planning to reuse substantial portions of the text in their own teaching material or internal wiki should establish the licensing position directly with the author rather than assume permission. This is a factual gap in the repository, not legal advice.

Maintenance cost is likewise undocumented. There is no CI configuration described, no dependency list and no note about which VuePress version the site targets. VuePress itself has had a major transition between its 1.x and 2.x lines, and a site built on one line does not migrate to the other without config changes. Nothing in the README indicates which line this site uses, so an upgrade estimate cannot be made from the available material. The practical consequence for a reader is small: the published pages keep working. The consequence for anyone considering a fork is larger, because you would inherit an unstated dependency surface.

When a different kind of resource is the better choice

If your goal is to learn Vue internals, the framework's own documentation and source repository are the primary reference, and this blog is a secondary interpretation of them. If your goal is to learn RAG or agents, vendor documentation and published papers will be more current than any personal notes site, because they are maintained by teams whose job is to keep them accurate. If your goal is to run a documentation site of your own, VuePress is the tool you would evaluate, and this repository is an example of its output rather than a guide to its configuration.

The real alternative here is not a competing blog. It is the distinction between a curated personal notebook and a maintained reference. A personal notebook wins on narrative continuity: one author, one voice, topics sequenced the way that author learned them, which is exactly why the interview and source-analysis sections read as a coherent path. A maintained reference wins on currency and on the ability to file a correction. Pick according to which property you need. For a topic like LeetCode patterns or JavaScript design patterns, the notebook's continuity is the more valuable property. For RAG, it is not.

Who should read it, and what to check first

Read it if you are a Chinese-speaking developer working through frontend fundamentals, Vue source code or early-stage LLM material and you want a single site that sequences those topics. The breadth is genuine: the README lists more than fifteen sections spanning algorithms, bundlers, TypeScript, testing and CSS preprocessors, which is a wide net for one person's notes.

Skip it if you need a dependency, a template, a maintained API reference, or content you can redistribute under a clear licence. Skip it too if you need English-language material, since the README and the linked pages are in Chinese.

What to verify before committing time: open the live site and confirm the specific page you need still exists at the path the README gives, since the README is the only index and the Gitee mirror is already marked abandoned. Then check whether the topic is one of the fast-moving ones (RAG, agents) or a stable one (Vue 2 analysis, LeetCode, Webpack 4). For the fast-moving pages, cross-check against primary sources. For the stable ones, the notes stand on their own.

Editorial conclusion

Read this repository if you want Chinese-language study notes on RAG, agents, Vue 2 and Vue 3 source code, LeetCode patterns or Webpack, Rollup and Vite basics, and you are willing to treat it as one person's notes rather than a maintained reference. Do not adopt it as a dependency, a template or a documentation platform for a team: the README lists content links and nothing else, the licence is not stated in the material provided, and there are no releases. Before relying on any page, open the live site at wangtunan.github.io/blog and check whether the topic you need is still covered, because the README is the only index and it is not versioned against the content.

Official sources

1. Issues
2. README
3. wangtunan/blog on GitHub