feat(phase-1): 정적 페이지를 Astro로 옮기고 Pages를 Actions로 고정한다

[gitgitWi]

스택: base main ← head feat/phase-1-scaffold

왜

Next.js 12 + yarn classic + JamesIves gh-pages 배포는 Astro static 전환과 bun 툴체인과 충돌한다. Phase 2(Content Collections) 전에 Astro 루트, StyleX 디자인시스템, Home/Tags 껍데기, GitHub Actions Pages 배포를 한 번에 고정해야 이후 페이즈가 같은 기준 위에서 쌓인다.

흐름

flowchart TD
  subgraph ASIS["AS-IS"]
    A1["Next pages + yarn.lock"] --> A2["JamesIves gh-pages + Node 14"]
    A2 --> A3["Astro/bun 전환 불가"]
  end
  subgraph TOBE["TO-BE"]
    B1["legacy-next 보관 + Astro 루트"] --> B2["StyleX DS + mock Home/Tags"]
    B2 --> B3["withastro/action + deploy-pages"]
    B3 -->|"성공"| B4["main 푸시 → Actions Pages"]
    B3 -->|"실패"| B5["Settings Pages Source=Actions 필요 — 사람 작업"]
  end
  style A3 fill:#ffebee,stroke:#c62828,color:#c62828
  style B4 fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32
  style B5 fill:#fff3e0,stroke:#e65100,color:#e65100

Loading

효과

flowchart LR
  P["이 PR"] --> U["사용자: Home/Tags 정적 페이지 공개"]
  P --> O["운영: bun.lock 감지 Actions 배포, yarn 제거"]
  P --> Q["품질: check/format/lint/test/build-storybook + Lighthouse 100"]

Loading

범위

flowchart TD
  subgraph IN["이번 PR"]
    I1["Astro 7 static + StyleX DS + Storybook 로컬"]
    I2["Home/Tags mock + deploy.yml 교체"]
  end
  subgraph NEXT["후속"]
    N1["Content Collections — phase-2 PLAN"]
    N2["ci.yml bun 게이트 — feat/ci-gates"]
  end
  subgraph OUT["제외"]
    X1["MDX 본문 — Phase 2"]
    X2["Storybook 배포 — 전 Phase 후 이슈"]
  end

Loading

검증

$ bun run check
Result (54 files):
- 0 errors
- 0 warnings
- 0 hints

$ bunx oxfmt --check .
All matched files use the correct format.
Finished in 558ms on 80 files using 8 threads.

$ bunx oxlint .
(exit 0)

$ bun run lint:stylex
$ eslint -c eslint.stylex.config.js src
(exit 0)

$ bunx vitest run
 Test Files  1 passed (1)
      Tests  1 passed (1)

$ bun run build
7 page(s) built in 484ms
Complete!

$ bun run build-storybook
Storybook build completed successfully

$ Lighthouse (local preview)
Home perf: 100  a11y: 100
Tags perf: 100  a11y: 100

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.