Enter content from home
The cockpit hero, pointer-tracking bot, planet navigation and backup Dock are in place, with a light 2D mobile fallback.
09 // MANUAL
Website manual
A visitor-first guide to what the site shows, what can be clicked, how content is maintained and what should improve next.
Visitor guide
This starts with what visitors can use directly, without treating homepage effects as the whole site.
Content pages
About, skills, projects, blog, travel, fitness, contact and terminal pages now form a complete public path.
Read and react
Blog posts use Markdown with search, detail pages, view and like APIs; KV enables persistent metrics when configured.
Life modules
Travel lights cities on a China map, while Fitness shows body stats, BMI, big-three lifts and a weekly plan.
Maintainable content
The admin console maintains Blog, Travel, Fitness, Skills, Projects and Contact content through GitHub API publishing for Markdown, JSON and uploads.
Launch basics
SEO metadata, canonical URLs, sitemap, robots and bilingual routing foundations are implemented.
Page guide
Each page has a defined job: presenting, recording, interacting or maintaining content.
Route: /en
Home
The first screen is the main visual entry. Visitors move the pointer to reveal planet labels and use planets or the Dock to enter routes.
Source: Page shell and home configuration
Route: /en/about
About
Explains positioning, presentation and implementation principles so visitors understand this is not only a portfolio.
Source: Site content configuration
Route: /en/skills
Skills
Organizes articles, files, links and awards by skill folder, with ongoing updates from admin.
Source: content/site/{locale}/skills.json
Route: /en/projects
Projects
Shows project cards and detail pages with problem, result, role, tags and public links.
Source: content/site/{locale}/projects.json
Route: /en/blog
Blog
Loads Markdown from content/blog with search, categories, tags, article detail pages, views and likes.
Source: Markdown frontmatter and body
Route: /en/travel
Travel
A China map shows visited cities; selecting a city opens date, cover, gallery, tags and notes.
Source: content/travel/{locale}/*.json
Route: /en/fitness
Fitness
Shows current height, weight, computed BMI, squat, bench, deadlift, phase goal and weekly training plan.
Source: content/fitness/{locale}/profile.json
Route: /en/contact
Contact
Shows confirmed public contact channels with copy buttons; missing or unconfirmed entries stay hidden, and phone stays hidden by default.
Source: content/site/{locale}/contact.json
Route: /en/terminal
Terminal
Uses commands to browse site information, simulated files and hidden routes as a security-themed interaction layer.
Source: Terminal command configuration
Maintainer notes
Maintainer notes stay in the second half and explain workflow without exposing secrets, passwords or private environment variables.
Login
ADMIN_PASSWORD validates access and sets an 8-hour HttpOnly cookie on success.
Content editing
Blog edits Markdown/frontmatter; Travel maintains cities, coordinates, cover, gallery and notes; Fitness uses forms for body stats, big-three lifts and weekly plans; Skills, Projects and Contact are also admin-maintained.
How to edit Skills, Projects and Contact
Open /en/admin and switch to Skills, Projects or Contact. Skills maintains folders, resources and awards; Projects maintains case copy, tags and links; Contact controls whether QQ, WeChat, email and phone are public, and missing or unconfirmed entries do not appear on public pages.
How to edit Travel and Fitness
Open /en/admin and switch to Travel or Fitness after login. Travel uploads can become cover or gallery images, common cities can fill coordinates, and Fitness plans can be edited by rows instead of raw JSON.
Publish and upload
When GitHub variables are complete, publishing writes to the repository and uploads images under public/uploads.
Fallback mode
Without GitHub configuration, public pages read local content and admin preview remains available while publish/upload are disabled.
Improvement ideas
The next priority is real content and environment validation before adding more easter eggs or complex motion.
P0
Real environment validation
Validate the GitHub publishing loop on cms-validation and configure KV REST to confirm views/likes persist across restarts.
P1
Real content and visual polish
Add real project cases, travel photos and training data while refining planet depth, mobile reading and page spacing.
P1
Admin form validation
Tighten validation for Travel coordinates, image paths, Fitness numbers and Markdown fields to reduce publishing mistakes.
P2
Content distribution and easter eggs
Add RSS, stronger search, terminal challenges and easter-egg progress without blocking the main user path.
P2
Richer 3D and motion
After performance is stable, expand R3F scenes, planet materials, bot states and light motion on secondary pages.