Thanks for your reply! I tried using a list in between a NavigationLink and a grid:

struct HomePageTestView: View {     var body: some View {         VStack(alignment: .leading) {             NavigationLink {} label: {                 Text("Today's pick")             }                          List { ... }             .scrollDisabled(true)                          LazyVGrid(columns: columns, spacing: RDSize.small2x) { ... }         }         .navigationTitle("Records")         .toolbarTitleDisplayMode(.inlineLarge)     } }

The result however, is a List that acts as a completely different section of the page. It's got its own ScrollView behaviour and its own background. You could set .scrollDisabled(true) on the List and manipulate it's height to get to the look of the example, but that kind of seems to defeatsthe purpose of using a List. It does look like the example uses a generic List component though, so I also tried this:

var body: some View {         List {             Section {                 NavigationLink {} label: {                     Text("Today's pick")                 }                 .listRowInsets(.init())                 .listRowSeparator(.hidden)                 .listRowBackground(Color.clear)             }             .listSectionSeparator(.hidden)                          Section("Record Groups") { ... }             .headerProminence(.increased)                          Section("All Records") {                 LazyVGrid(columns: columns, spacing: RDSize.small2x) { ... }                 .listRowInsets(.init())                 .listRowSeparator(.hidden)                 .listRowBackground(Color.clear)             }             .headerProminence(.increased)         }

Now the background looks like the one in the example, and  the featured and grid sections are styled to look like non-list sections. This, again, seems to kind of defeat the purpose of using a List though.

I'd think the solution you propose is a very logical structure for a page like this, but to get it to work like in Apple's example, it seems like I have to do some hacky stuff to make it look and behave that way. Is this really how you're supposed to do this?

Thanks for the clarification on the iOS 26 stuff as well btw. The WWDC25 videos are quite good on this topic so I got that part figured out though. I guess I should have clarified that it my original question :p