Skip to content

???????????? SSR ????? #255

@yeyixiang2007

Description

@yeyixiang2007

What to build

Make an explicit product/engineering choice for the search page rendering strategy, then implement the page so it follows that strategy cleanly. The current behavior pays for a server-rendered shell while still fetching the real search results on the client. We need either true SSR data delivery for SEO-sensitive search or a deliberate CSR path optimized for lower server cost.

Acceptance criteria

  • The team documents and applies a clear rendering strategy for /search (SSR-first or CSR-first).
  • The page no longer combines SSR shell cost with a redundant first search fetch.
  • Search results, filters, pagination, and rate-limit handling still work under the chosen strategy.
  • Verification captures the before/after request pattern for the first search page load.

Blocked by

None - can start immediately

Metadata

Metadata

Assignees

No one assigned

    Labels

    HITLHuman-in-the-loop: 需人工决策enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions