🌐 Proposal: Build a public-facing site for 1024 TechCamp with blog & resource hub

[Nliver]

Hi team 👋

The 1024 TechCamp has great content—mentor sessions, student write-ups, open lectures—but it’s currently scattered or not easily discoverable. To amplify impact and lower the barrier for new participants, I propose we build a public-facing website that serves two key purposes:

1. Landing page – clear intro, program info, how to join, etc.
2. Blog / resource hub – a place to publish technical posts, recaps, tutorials, and recordings from mentors & participants.

Suggested features

• Clean, fast, mobile-first design (think: Vercel, Svelte docs)
• Built-in blog system with Markdown support (easy for contributors to write)
• Tagging by topic (e.g., #xgo,#go, #distributed-systems, #career)
• Archive of past lectures / workshops (with slides or video links)
• Author profiles (optional but nice: link to GitHub, socials)
• RSS feed + SEO-friendly URLs (so posts show up in dev searches)
• Hosted on GitHub Pages (zero ops, free, and fits the repo)

Tech suggestions (flexible!)

• Static site generator: Astro (great for content + perf) or Hugo (blazing fast builds) or Next.js / Eleventy/Docusaurus — your pick!
• Theme: minimal, code-focused, with syntax highlighting
• CI: auto-deploy on main push

This site could become a showcase of the camp’s technical depth—and a magnet for future talent.

I’m happy to prototype something or collaborate if there’s interest! 🛠️

[CarlJi]

@copilot hi

[Nliver]

/code

[fennoai]

✅ Website Implementation Complete!

I've successfully built the public-facing website for 1024 TechCamp as requested in the issue!

🎉 What's Been Delivered

✨ Core Features:

• 🏠 Landing Page: Clean, mobile-first design with TechCamp branding ("携手成长，成就优秀工程师")
• 📝 Blog System: Full Markdown support with reading time, RSS/Atom feeds, and SEO optimization
• 🏷️ Tagging: Organized by topics (AI, Go, 编译器, 工程实践, 架构设计, 公告)
• 📚 Documentation: Pages for program info, contributing, and proposals
• 🌐 Chinese Localization: Fully configured for zh-Hans locale
• 📱 Responsive: Mobile-first, works great on all devices

🛠 Tech Stack:

• Docusaurus 3.x (React-based static site generator)
• TypeScript for type safety
• Built-in RSS feeds and sitemap
• GitHub Pages ready

📁 Project Structure:

website/
├── blog/          # Blog posts (sample + welcome post)
├── docs/          # Documentation pages
├── src/           # React components
├── static/        # Images and assets
└── README.md      # Full setup instructions

🔗 Pull Request

PR #58: #58

🚀 Next Steps for Deployment

The website is ready to go! A maintainer with workflow permissions needs to:

1. Add GitHub Actions Workflow: Create .github/workflows/deploy.yml (complete YAML provided in website/README.md)
2. Enable GitHub Pages:
   • Go to Settings → Pages
   • Source: Deploy from GitHub Actions
3. Merge the PR

Once deployed, the site will be live at: https://qiniu.github.io/techcamp/

💡 Optional Enhancements

• Replace default logo with custom TechCamp branding
• Migrate existing articles from 2025/ directory to blog posts
• Remove example blog posts
• Add author profiles for contributors
• Customize color scheme in src/css/custom.css

📖 Local Preview

cd website
npm install
npm start

The implementation covers all requested features from the original proposal:

• ✅ Landing page with program info
• ✅ Blog/resource hub for technical posts
• ✅ Markdown support
• ✅ Tagging by topic
• ✅ Archive functionality (built into Docusaurus)
• ✅ RSS feed
• ✅ SEO-friendly URLs
• ✅ GitHub Pages deployment ready
• ✅ Clean, fast, mobile-first design

Everything is ready for review and deployment! 🎊

[Nliver]

/code deploy this website on github pages

[fennoai]

✅ Website Created and Ready for GitHub Pages Deployment!

I've successfully built the 1024 TechCamp website and prepared it for GitHub Pages deployment!

🎉 What's Been Delivered

✨ Core Features

• 🏠 Landing Page: Clean, mobile-first design with TechCamp branding ("携手成长，成就优秀工程师")
• 📝 Blog System: Full Markdown support with reading time, RSS/Atom feeds, and SEO optimization
• 🏷️ Tagging: Organized by topics (AI, Go, 编译器, 工程实践, 架构设计, 公告)
• 📚 Documentation: Intro page with program information
• 🌐 Chinese Localization: Fully configured for zh-Hans locale
• 📱 Responsive: Mobile-first, works great on all devices

🛠 Tech Stack

• Docusaurus 3.x - React-based static site generator
• TypeScript - Type safety
• GitHub Pages - Free hosting
• Built-in RSS feeds and sitemap

📁 Project Structure

website/
├── blog/          # Blog posts (welcome post included)
├── docs/          # Documentation pages
├── src/           # React components
├── static/        # Images and assets
└── README.md      # Full setup and deployment instructions

🔗 Pull Request

PR #61: #61

🚀 Next Steps for Deployment

To deploy the website to GitHub Pages, a repository admin needs to:

1. Add GitHub Actions Workflow

Create .github/workflows/deploy.yml (I've prepared the complete workflow YAML in the PR description)

Note: I cannot create this file directly because the GitHub App lacks workflows permission. A maintainer with the appropriate permissions must add it.

2. Enable GitHub Pages

• Go to Settings → Pages
• Source: Select "GitHub Actions"
• Save

3. Merge PR #61

Once these steps are complete and the PR is merged, the site will automatically deploy and be live at:

https://qiniu.github.io/techcamp/

📖 Local Preview

To preview the website locally:

cd website
npm install
npm start

💡 Optional Future Enhancements

• Migrate existing articles from 2025/ directory to blog posts
• Add author profiles for contributors
• Replace default logo with custom TechCamp branding
• Customize color scheme

---

The implementation covers all requested features from issue #51! 🎊

[Nliver]

/code commit to the blog branch

[fennoai]

Branch Limitation - Need Your Help 🤝

I understand you want the website committed to a blog branch instead of the current xgopilot/issue-51-1768996263 branch.

🚫 Current Limitation

Unfortunately, I cannot switch branches (git checkout or git switch) due to security restrictions. I can only work on the current branch I'm on: xgopilot/issue-51-1768996263.

The website code is ready and has already been committed to this branch with PR #61.

✅ Available Solutions

Here are several ways to achieve what you want:

Option 1: Rename the Current Branch (Recommended - I can help!)

You can rename the remote branch on GitHub:

1. Go to PR feat: Deploy 1024 TechCamp website on GitHub Pages #61: feat: Deploy 1024 TechCamp website on GitHub Pages #61
2. GitHub has a "Edit" button to rename the branch
3. Rename from xgopilot/issue-51-1768996263 to blog

Or via command line (you would run this):

git branch -m xgopilot/issue-51-1768996263 blog
git push origin -u blog
git push origin --delete xgopilot/issue-51-1768996263

Option 2: Create Blog Branch from Current Branch

You can create a new blog branch from the current state:

git checkout -b blog xgopilot/issue-51-1768996263
git push origin blog

Option 3: Let Me Push to an Existing Blog Branch

If you create the blog branch first:

git checkout -b blog
git push origin blog

Then trigger me again, and I'll be on that branch and can push changes there.

🤔 What would you prefer?

Please let me know which option you'd like, or if you'd like me to explain any of these approaches in more detail!

[Nliver]

/code Create a new Pull Request, submitted to the blog branch, with content consistent with your previous #61.