Why I Built This Website

I have worked on many Django projects. I often use Python to solve data processing problems. As my project experience grew, I felt I needed a platform. This platform would help me record and share my development experiences.

Why I Built This Site

I built this website for several reasons:

• Knowledge Storage: I want to organize my scattered project experiences. This creates a reusable knowledge base.
• Experience Sharing: I share technical insights and practical experiences. This helps me learn from other developers.
• Personal Brand: I want to build a professional image. This increases my visibility in the tech field.
• Sustainable Growth: I create quality content to attract readers. This explores ways to monetize knowledge.

When I need to copy old code or find a technical solution, this website becomes my "external brain". I also hope this content helps other developers. This creates a positive tech ecosystem.

Technology Stack

• Website Framework: VitePress - Thanks to the VitePress team
• Article Writing: Markdown
• Data Processing: JavaScript scripts update index.md and sidebar after adding new articles
• Development Tool: Qoder
• CI/CD: Github
• Deployment: Cloudflare Pages

Article Publishing Process

• I write articles in Chinese first. Then I translate them to create English versions. Yes, my website is bilingual!
• I use JavaScript scripts to refresh article index pages and sidebar content.
• I commit to Github repository. Cloudflare Pages automatically deploys the changes.

Development Experience

I don't know JavaScript. So I rely on prompts and AI development tools to build features. On the blog homepage, you can click article tags. This jumps to the tag page. The tag page shows all articles under that tag. I debugged this feature for a long time. It took about 4 hours. Finally I completed it.

AI tools have a special characteristic. They generate lots of code. But the code isn't always correct. You need repeated communication and gradual improvements. The most annoying thing happens often. You spend great effort to fix feature A. Then you develop feature B. Feature A breaks again. You need to fix feature A again. This is very troublesome.

I suggest good version management. Commit good versions promptly after you perfect the current version. When you find problems with feature A, rollback quickly.

Next Steps

• Use Cloudflare's D1 database to develop article comments. This will help me interact with readers.
• Add subscription functionality to collect user email lists.
• Bind a domain name when I have 10 articles.

Today is August 27, 2025. Let's see how long it takes me to complete these plans.