dong.nguyen efcb3cbef9 feat(timeline): connect every node to its title with a hairline
Drawn from .timeline-marker::after rather than from the entry or the header, because the current-role entry pads its own content box while the marker is pinned to the spine: left 10px, top 3px, width 24px on the 36px gutter (16px on the 28px mobile gutter) — the same x 12 to x 36 arithmetic .timeline-tldr::after already uses. The link carries the node's own ink: --border-strong for an ordinary ring and the gap node, --accent for the two ends of the timeline (the first node and the TLDR diamond, whose link already exists), and it follows the ring through the hover transition. The current-role link stops at the panel's accent edge (x 28 desktop, x 24 mobile). Spec: spec-ui-experience.md, new §Node → Title Link.
2026-10-21 00:01:04 +07:00
2026-10-12 14:56:48 +07:00
2026-10-16 21:14:59 +07:00
2026-10-19 18:51:27 +07:00
2026-10-04 09:34:55 +07:00
2026-10-09 21:29:59 +07:00
2026-10-19 18:51:27 +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%