Explain how to use searchParams prop

[gaearon]

I think this is a glaring omission from the docs that makes it very difficult to understand how to use these API right.

See this discussion on Reddit.

I took a minimal approach but really this should be properly explained somewhere because nobody knows this prop exists.

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: 9dbd19c

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[icyJoseph]

Let's merge this, and plan an additional section to:

• https://nextjs.org/docs/app/getting-started/layouts-and-pages

### Creating a dynamic segment

... content

### Using search params

A Guide: searchParams and useSearchParams is probably a good idea too, there's a bunch of patterns we haven't expanded upon, and cause people to run into issues, like: #61654

(Titles are not final)

[Ephem]

I've found passing searchParams down to Client Components can be a bit of an anti-pattern since there are situations where you might update them without revalidating the Server Component.

This can happen when doing "shallow" updates, that is, call window.history.pushState (or replace) directly, which updates the page without going to the server, as described in Shallow routing on the client.

This is a pretty popular approach because nuqs does it by default, so maybe mentioning you can do that here without additional context (which might be out of place here?) might lead some people down a painful path?

I don't have strong feelings though and think this is a great update to the docs, just wanted to mention it!

[icyJoseph]

Taking this into account for a Getting Started/Guide section.