wangtunan/blog is a VuePress 2 site where the posts are the repository
Personal blog documenting a journey of growth. https://wangtunan.github.io/blog/
At a glance
- What is it?
- This is a personal technical blog built on VuePress 2, still pinned to release candidate versions, with posts on Vue source, TypeScript, bundlers and algorithms living directly in the repository. Useful as a reading reference and as a VuePress setup example, not as a tool.
- Who is it for?
- Use this repository as a reading reference if you are working through Vue 2 or Vue 3 internals, TypeScript type challenges or bundler internals and want one person's notes in Chinese, or as a VuePress 2 reference setup if you want a small site with comments, KaTeX math and Prism highlighting already wired. Do not adopt it as a base for your own site without expecting to unpick the RC pins and the single-author dependency list.
- 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?
- Activity is slowing. The repository last received commits 8 months ago.
- What is it written in?
- Mainly Shell, according to GitHub's language statistics.
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
- wangtunan/blog391 ★ · +0
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| wangtunan/blog | 391 | 391 |
0 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The repository is the site, with no build output committed
Top-level entries are `.github/`, `.gitignore`, `.vscode/`, `README.md`, `depoly.sh`, `docs/`, `donate.jpg` and `package.json`. All content lives under `docs/`, which is the directory the build consumes, and there is no generated site directory in the tree.
`package.json` declares `"type": "module"` and carries exactly three scripts. Dev and build are the stock VuePress commands pointed at `docs`:
vuepress dev docs
vuepress build docsThe third is `"depoly": "depoly.sh"`, and the misspelling of deploy is consistent: the script name, the command and the shell file at the root all read `depoly`. That is a small thing, but it is the kind of detail that costs a newcomer a grep, and it also tells you the deployment path is a shell script the author maintains by hand rather than a hosted build integration. The repository's primary language is recorded as Shell for that reason.
There is no published package on any registry and no release history. Consuming this project means reading it, or forking it.
Every VuePress dependency is still a release candidate
The dependency situation is the first thing to check before planning anything around this site. The single runtime dependency is `vuepress` at `^2.0.0-rc.21`. Every plugin is on a different release candidate line, `^2.0.0-rc.94`: `@vuepress/bundler-vite`, `@vuepress/plugin-baidu-analytics`, `@vuepress/plugin-comment`, `@vuepress/plugin-markdown-math`, `@vuepress/plugin-register-components`, `@vuepress/plugin-prismjs` and `@vuepress/theme-default`.
So the site runs on a bundler whose API is still moving, on plugins whose APIs are still moving, and the caret ranges mean a fresh install can pull a later candidate than the one this content was written against. Two supporting packages are pinned separately: `katex` at `^0.16.22`, which serves the math rendering, and `sass-embedded` at `^1.86.3`, a Dart Sass implementation used by the theme's stylesheets.
`@vuepress/plugin-baidu-analytics` is the one that decides who can fork this. Baidu analytics is a China-market analytics script, so the fork inherits a tracker pointing at a service the reader may have no way to reach. Nothing in the repository documents removing it.
Comments, math and highlighting are plugin choices, not conventions
Three of the plugins tell you what a reader experiences here. `@vuepress/plugin-comment` adds comment threads, which is why the site reads as a discussion space rather than a read-only archive. `@vuepress/plugin-markdown-math` together with `katex` renders formulas inline in the prose, which matters for the notes that walk through algorithm behaviour. `@vuepress/plugin-prismjs` does code highlighting instead of VuePress shipping a default.
`@vuepress/plugin-register-components` is the least visible and the most structural. It lets components be registered for use across many Markdown files without importing them into each one, which is how a notes site avoids editing forty posts to add a diagram component.
The bundler is `@vuepress/bundler-vite`, so Vite does the build rather than webpack. That matters if you plan to copy this setup: VuePress 1 used webpack, and most of the advice and plugin examples written for VuePress 1 assume webpack and will not transfer.
Together these seven plugins are the whole feature surface. There is no search, no sitemap configuration, no i18n and no deployment workflow file in the repository, which for a blog with this many pages is a deliberate-looking absence rather than an oversight worth guessing about.
The catalogue spans framework internals, tooling and algorithms
The README is an index, and reading it as one tells you what this author was working through. Vue source analysis appears twice, for Vue 2.0 and Vue 3.0, each with its own introduction page, which is the deepest material in the collection and the part that ages best, since framework internals change more slowly than tooling does.
Tooling gets three separate entries: Webpack 4 fundamentals, Rollup fundamentals and Vite fundamentals. That trio is dated in a specific way. Webpack 4 predates the version most teams now use, so that page describes a configuration style the current ecosystem has moved past, while the Vite page is the one that matches current practice.
TypeScript has a fundamentals page and a type challenges page, and the challenges page is the more distinctive of the two, since type-level exercises are less common in this kind of index than framework notes.
Then there is the algorithms and interview material: a data structures and algorithms foundation, a LeetCode section, a frontend interview section, Python quickstart and advanced techniques, SASS fundamentals, Vue application testing, VuePress fundamentals, and reading notes on You Don't Know JavaScript in three volumes, ES6 in depth, JavaScript design patterns, and JavaScript data structures and algorithms.
Two newer headings sit at the top, a RAG basics page and an agent fundamentals page. They are the only entries that read as recent work rather than accumulated study notes, and they are the only two that point away from front-end topics entirely.
The GitHub Pages site is live and the Gitee mirror is marked abandoned
The README gives two addresses. The GitHub Pages site at `https://wangtunan.github.io/blog/` is the current one. The Gitee mirror at `http://wangtunan.gitee.io/blog/` carries the marker 已废弃, meaning abandoned or discontinued, so it is kept for the record rather than as a working alternative. Anyone landing on the mirror URL should treat its contents as a frozen snapshot.
What is not documented anywhere in the repository is how `depoly.sh` actually deploys, whether it pushes to a `gh-pages` branch, and whether it expects a `base` path configured for the GitHub Pages subdirectory. A fork serving from a different username or a project page rather than a user page will render with broken asset paths unless something in that script or a VuePress `base` setting accounts for it, and neither is visible from the files listed here.
The same applies to the analytics plugin. If you fork this to study VuePress configuration, knowing which part of the build is author-specific is more useful than knowing which plugins are present.
Activity is tracked by hand in a heading with nothing under it
The README has a section headed 仓库活跃度, meaning repository activity, and it is empty. No chart, no date, no text. That is the only activity signal in the project.
The underlying fact is narrower than a contributor might want. The last push to the default branch, `master`, was on 2026-03-13. There are no GitHub releases, no version tags to compare against, and the package has no version field in `package.json`, so there is no way to date a content change from inside the repository. What you can do is read the commit history on the default branch and check whether the VuePress dependencies have been refreshed past the release candidate lines above.
Nothing here should be described as actively developed. A blog with a fixed set of finished notes is a different kind of artefact from a library, and judging it by release cadence is the wrong lens. Judge it by whether the specific page you came for is still accurate, which is a per-page question this repository gives you no tooling to answer.
Licensing is the other absence. The repository carries no licence file among its top-level entries and the licence field is unrecorded, so the notes are readable but not licensed for reuse. Ask before copying a page elsewhere.
Editorial conclusion
Use this repository as a reading reference if you are working through Vue 2 or Vue 3 internals, TypeScript type challenges or bundler internals and want one person's notes in Chinese, or as a VuePress 2 reference setup if you want a small site with comments, KaTeX math and Prism highlighting already wired. Do not adopt it as a base for your own site without expecting to unpick the RC pins and the single-author dependency list. Verify first what you actually need from it, because it is a blog rather than a library: there is no package to install, no API, and the last push was on 2026-03-13.
Frequently asked questions
What is in the wangtunan/blog repository?
It is a personal blog built with VuePress 2, with all posts stored as Markdown under `docs/`. The top-level files are `.github/`, `.gitignore`, `.vscode/`, `README.md`, `depoly.sh`, `docs/`, `donate.jpg` and `package.json`.
How do I run the wangtunan/blog site locally?
The package defines a dev script whose command is `vuepress dev docs` and a build script whose command is `vuepress build docs`. There is no documented install command in the repository, so dependencies come from the lists in `package.json`.
Is wangtunan/blog usable as a VuePress starter?
It is a single-author site pinned to release candidates, including `vuepress` at `^2.0.0-rc.21` and its plugins at `^2.0.0-rc.94`. It also carries `@vuepress/plugin-baidu-analytics`, which a fork would inherit.
What topics does wangtunan/blog cover?
The index covers Vue 2.0 and Vue 3.0 source analysis, Webpack 4, Rollup and Vite, TypeScript fundamentals and type challenges, data structures and algorithms, LeetCode, frontend interview preparation, Python, SASS, Vue testing and VuePress, plus reading notes on several JavaScript books and two newer pages on RAG and agent fundamentals.
What licence applies to the wangtunan/blog posts?
The repository lists no licence file at its top level and the licence field is unrecorded, so the notes carry no stated reuse terms. The README instead asks readers for a star or a donation, with `donate.jpg` at the root.
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/wangtunan-blog)Star history chart for your README
[](https://hysenlabs.com/projects/wangtunan-blog)Was this useful?