ce6110588f
- Created `src/pages/contact.astro` and `src/pages/zh/contact.astro` to support multilingual contact functionality. - Introduced `contactIntents` and `contactMethods` dynamic configurations in `src/lib/data/contact.ts` for streamlined content management. - Designed responsive and localized layouts with enhanced UX for both languages.
258 lines
4.6 KiB
Markdown
258 lines
4.6 KiB
Markdown
# Personal Website Rebuild Plan (Advanced Engineer Version)
|
||
|
||
Author: Zhao Guiyang
|
||
Website: https://zhaoguiyang.com
|
||
|
||
Goal:
|
||
Transform the website from a generic portfolio into an **engineering-focused personal site** that communicates real experience, technical thinking, and current work.
|
||
|
||
The site should resemble professional developer sites such as those of senior engineers, not template demo portfolios.
|
||
|
||
---
|
||
|
||
# 1 Core Positioning
|
||
|
||
Professional identity to communicate:
|
||
|
||
Senior Frontend Engineer
|
||
Full-stack Developer
|
||
AI-assisted Development Practitioner
|
||
|
||
Key signals:
|
||
|
||
- 8 years web development experience
|
||
- Complex enterprise system development
|
||
- Financial and blockchain infrastructure platforms
|
||
- Frontend architecture and engineering practices
|
||
- AI-assisted development workflows
|
||
|
||
Avoid generic descriptions such as "passionate developer".
|
||
|
||
Focus on **real engineering capability**.
|
||
|
||
---
|
||
|
||
# 2 Website Structure
|
||
|
||
The site should contain the following pages.
|
||
|
||
Home
|
||
About
|
||
Projects
|
||
Writing
|
||
Now
|
||
Uses
|
||
Contact
|
||
|
||
Each page must be concise and information-dense.
|
||
|
||
---
|
||
|
||
# 3 Home Page
|
||
|
||
Purpose: immediate identity signal.
|
||
|
||
Structure:
|
||
|
||
Name
|
||
|
||
Short identity line:
|
||
|
||
Senior Frontend Engineer building complex systems and AI-assisted products.
|
||
|
||
Short introduction (2–3 sentences):
|
||
|
||
Zhao Guiyang is a web developer with 8 years of experience building financial platforms, enterprise systems, and blockchain infrastructure.
|
||
|
||
He focuses on frontend architecture, complex system design, and AI-assisted development workflows.
|
||
|
||
Links section:
|
||
|
||
Projects
|
||
Writing
|
||
GitHub
|
||
Contact
|
||
|
||
---
|
||
|
||
# 4 About Page
|
||
|
||
This page explains the developer's background and technical focus.
|
||
|
||
Sections:
|
||
|
||
Background
|
||
|
||
Zhao Guiyang is a web developer with extensive experience building enterprise systems and financial platforms.
|
||
|
||
His work focuses on frontend engineering architecture and complex business systems.
|
||
|
||
Technical Focus
|
||
|
||
Frontend architecture
|
||
Large-scale enterprise applications
|
||
Financial and blockchain systems
|
||
AI-assisted development workflows
|
||
|
||
Experience
|
||
|
||
8 years of professional development experience.
|
||
|
||
Participation in multiple government and financial technology systems including trading platforms, blockchain infrastructure, and industrial management systems.
|
||
|
||
---
|
||
|
||
# 5 Projects Page (Engineering Case Studies)
|
||
|
||
Replace demo projects with real engineering work.
|
||
|
||
Each project should include:
|
||
|
||
Project name
|
||
System type
|
||
Description
|
||
Technical challenges
|
||
Responsibilities
|
||
Results
|
||
|
||
Example structure:
|
||
|
||
Project: Digital Securities Trading Platform
|
||
|
||
System Type:
|
||
Financial blockchain trading platform
|
||
|
||
Description:
|
||
A digital asset trading system supporting multi-role financial institutions.
|
||
|
||
Technical Challenges:
|
||
|
||
Complex role-based permissions
|
||
Financial system stability requirements
|
||
Blockchain wallet integration
|
||
|
||
Responsibilities:
|
||
|
||
Frontend module architecture
|
||
User management system refactor
|
||
Bank login integration
|
||
|
||
Results:
|
||
|
||
System stability reached 99.5% uptime.
|
||
|
||
---
|
||
|
||
Include these real projects:
|
||
|
||
Digital Securities Trading Platform
|
||
Blockchain BaaS Platform
|
||
Supply Chain Finance Platform
|
||
Industrial Smart Park Management System
|
||
|
||
Do not include demo projects.
|
||
|
||
---
|
||
|
||
# 6 Writing Page
|
||
|
||
Purpose: demonstrate technical thinking.
|
||
|
||
Blog topics should focus on engineering experience.
|
||
|
||
Examples:
|
||
|
||
Designing complex permission systems
|
||
Optimizing large file uploads
|
||
Frontend architecture for financial platforms
|
||
AI-assisted development workflow
|
||
|
||
Avoid beginner tutorials.
|
||
|
||
---
|
||
|
||
# 7 Now Page
|
||
|
||
Purpose: show current activity.
|
||
|
||
Content example:
|
||
|
||
Currently exploring AI-assisted software development.
|
||
|
||
Building developer tools and experimenting with AI product ideas.
|
||
|
||
Working on open-source tools and automation.
|
||
|
||
---
|
||
|
||
# 8 Uses Page
|
||
|
||
List tools used in daily development.
|
||
|
||
Example:
|
||
|
||
Editor:
|
||
VS Code
|
||
|
||
Languages:
|
||
TypeScript
|
||
JavaScript
|
||
|
||
Frameworks:
|
||
React
|
||
Vue3
|
||
|
||
Tools:
|
||
Git
|
||
Docker
|
||
Node.js
|
||
|
||
AI Tools:
|
||
ChatGPT
|
||
Claude
|
||
AI-assisted development workflows
|
||
|
||
---
|
||
|
||
# 9 Contact Page
|
||
|
||
Provide minimal contact methods.
|
||
|
||
Email
|
||
GitHub
|
||
LinkedIn (optional)
|
||
|
||
Avoid excessive personal information.
|
||
|
||
---
|
||
|
||
# 10 Design Principles
|
||
|
||
The website should follow these rules:
|
||
|
||
Minimalist design
|
||
Text-focused content
|
||
Fast loading
|
||
No heavy animations
|
||
No unnecessary UI complexity
|
||
|
||
Content clarity is more important than visual effects.
|
||
|
||
---
|
||
|
||
# 11 Execution Rules for AI
|
||
|
||
The executing AI must follow these rules:
|
||
|
||
Do not fabricate projects.
|
||
Do not invent work experience.
|
||
Do not add technologies not present in the resume.
|
||
Maintain concise technical writing style.
|
||
Preserve the current UI layout if possible.
|
||
|
||
Only update textual content and project listings.
|
||
|
||
---
|
||
|
||
# End of Document
|