dong.nguyen 4387f889f5 feat(motion): standardize animation recipes across sections and pages
- Replace the AnimatedSection wrapper with the per-section recipe: InView
  wrapping motion.section with initial="hidden" whileInView="visible" and
  viewport={{ once: true, amount: 0.1 }}; delete AnimatedSection.tsx
- Apply the item recipe (opacity/y 24, amount 0.2, delay i * 0.08) to timeline
  entries, philosophy/expertise/project cards, hero blocks, contact links and
  project-detail blocks
- Move transforms into motion: whileHover/whileTap on cards, links and Button;
  CSS :hover keeps only colour/border/shadow, and `transition: all` becomes an
  explicit property list so motion owns the transform
- Rebuild HeroParticles as perspective-projected depth tiers with scroll-linked
  transforms, no mask-image, plus a documented reduced-motion caveat
- Update AGENTS.md motion section and spec-v3-ui-enhancements /
  spec-v3-mobile-navigation progress notes
2026-10-17 20:02:47 +07:00
2026-10-12 14:56:48 +07:00
2026-10-16 21:14:59 +07:00
2026-10-16 21:14:59 +07:00
2026-10-17 15:58:40 +07:00
2026-10-04 09:34:55 +07:00
2026-10-09 21:29:59 +07:00
2026-10-15 15:00:22 +07:00
2026-10-10 14:14:05 +07:00
2026-10-04 09:34:55 +07:00
2026-10-09 21:29:59 +07:00

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.

Currently, two official plugins are available:

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the Oxlint configuration

If you are developing a production application, we recommend enabling type-aware lint rules by installing oxlint-tsgolint and editing .oxlintrc.json:

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "plugins": ["react", "typescript", "oxc"],
  "options": {
    "typeAware": true
  },
  "rules": {
    "react/rules-of-hooks": "error",
    "react/only-export-components": ["warn", { "allowConstantExport": true }]
  }
}

See the Oxlint rules documentation for the full list of rules and categories.

Deployment On Windows

Open PowerShell on your Windows computer.

Create an ssh key for gitea deployment:

ssh-keygen -t ed25519 -C "gitea-deploy" -f "$HOME\.ssh\gitea_deploy_key"

In a VPS server, create the deployment user

sudo adduser gitea-deployer
sudo usermod -aG docker gitea-deployer
# test user can run docker
sudo -u gitea-deployer docker ps
sudo install -d -m 700 -o gitea-deployer -g gitea-deployer /home/gitea-deployer/.ssh

Because no ssh-copy-id is available on Windows, you need to copy the public key to the server manually.

type $HOME\.ssh\gitea_deploy_key.pub | ssh gitea-deployer@112.213.91.239 -p 2212 "cat >> ~/.ssh/authorized_keys"

Test ssh connected with a private key

ssh gitea-deployer@112.213.91.239 -p 2212 -i "$HOME\.ssh\gitea_deploy_key" -o IdentitiesOnly=yes

Get content of private key

Get-Content -Raw "$HOME\.ssh\gitea_deploy_key"

In Gitea, create action secrets DEPLOY_HOST, DEPLOY_SSH_PORT, DEPLOY_USER, DEPLOY_SSH_PRIVATE_KEY for deployment.

S
Description
No description provided
Readme
14 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 81.8%
CSS 15.3%
HTML 2.9%