Notes on Next 16 and the app router

The biggest practical change is that route props are async, so detail pages and search pages need to await params or searchParams explicitly. Once that is absorbed, the mental model stays clean.

For a content site, the default strategy should still be static generation. Use dynamic work only where the data truly changes at request time or where personalization exists.

The app router is most effective when layouts, metadata, and content boundaries are treated as product architecture, not just folder structure.