???????????????

[yeyixiang2007]

What to build

Reduce homepage request cost end-to-end so the public homepage no longer pays for SSR shell rendering plus a second client-side data fetch. The homepage should deliver its first screen with one coherent data-loading path that matches the chosen Nuxt rendering mode and avoids unnecessary API round-trips.

Acceptance criteria

• Homepage first-screen data is loaded through a single intentional path instead of SSR shell plus client re-fetch duplication.
• The homepage remains functionally correct for banners, recommendations, hot courses, recent updates preview, and college entry.
• Tests cover the chosen data-loading path and prevent regression to duplicate first-screen fetches.
• Basic verification records the before/after homepage request count for an anonymous visit.

Blocked by

None - can start immediately

[yeyixiang2007]

Completed a small homepage request-cost slice. The desktop homepage first screen now loads through a single useAsyncData path instead of SSR shell plus client-side refetch, and the mobile homepage feed component is no longer mounted on desktop pages just to be hidden by CSS. Verification: pnpm --filter scustack-web test -> 67 passed; pnpm --filter scustack-web build succeeded. Request-count note: before this change an anonymous desktop visit triggered the homepage aggregate and colleges fetch again on mount, and also mounted the hidden mobile feed component; after this change first-screen homepage/colleges data comes from useAsyncData, while onMounted is used only for banner rotation and later recent-updates pagination.