<!--
{
  "availability" : [
    "iOS: 18.0.0 -",
    "iPadOS: 18.0.0 -",
    "macCatalyst: 18.0.0 -",
    "macOS: 15.0.0 -",
    "tvOS: 18.0.0 -",
    "visionOS: 2.0.0 -",
    "watchOS: 11.0.0 -"
  ],
  "documentType" : "symbol",
  "framework" : "SwiftUI",
  "identifier" : "/documentation/SwiftUI/SectionConfiguration/content",
  "metadataVersion" : "0.1.0",
  "role" : "Instance Property",
  "symbol" : {
    "kind" : "Instance Property",
    "modules" : [
      "SwiftUI"
    ],
    "preciseIdentifier" : "s:7SwiftUI20SectionConfigurationV7contentAA18SubviewsCollectionVvp"
  },
  "title" : "content"
}
-->

# content

The contents of the section body.

```
var content: SubviewsCollection { get }
```

## Discussion

Notably, the section’s content is a `SubviewsCollection`, not a
`Subview`, as it can be made up of multiple subviews. That means in most
cases, the subviews collection should be treated as a collection (either
indexed into, or used with a `ForEach`), or the subviews collection
should be wrapped in a container view, like a layout, or other custom
container:

```
PinboardSectionsLayout {
    ForEach(sections: content) { section in
        VStack {
            section.content
        }
    }
}
```

Here, we want to create one view for `PinboardSectionsLayout` to place
per section in content. To do that, we surround the `ForEach` body in
another container, a `VStack` layout, ensuring the different subviews of
section.content are treated as a single view by the surrounding layout.

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)