itwanger / itwanger/toBeBetterJavaer

fix: migrate README CDN images + clean China-only references + Algolia cleanup

Open
#208 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
17.7k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Description

What was done

1. README.md CDN migration (4 images)

All cdn.paicoding.com images in README.md migrated to self-hosted CDN (raw.githubusercontent.com/acailic/javasi-cdn/master/):

  • logo.png (uploaded to javasi-cdn repo)
  • tobebetterjavaer-map.png (already existed)
  • stutymore/README-20241106103513.png (uploaded)
  • stutymore/README-20230829162301.png (uploaded)
2. README.md China-only reference cleanup
  • Removed old domain link tobebetterjavaer.com
  • Removed paicoding.com/column/5/1 (Jishupai column)
  • Removed Gitee link (China-only platform)
  • Badge links redirected javabetter.cn -> javasi.dev
  • GitHub links redirected itwanger/toBeBetterJavaer -> acailic/toBeBetterJavaer
  • VuePress Theme Hope link fixed from /zh/ to English version
  • Paicoding friendly-link shortened (removed Jishupai reference)
3. Algolia docsearch comment cleanup in theme.ts

Stale reference to tobebetterjavaer Algolia index replaced with clear comment that local search is enabled automatically.

Remaining

  • 124 external links to Chinese platforms (bilibili, zhihu, csdn) in docs/src/ are reference links in articles, not monetization — they stay
  • Build verification and deploy

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the completed changes in README.md and theme.ts, and verify that the remaining docs/src/ Chinese-platform links are intentionally retained as article references. Start with the project’s build process, then confirm the documentation builds successfully and is ready for deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation, release
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.