Section¶
Render the semantic section landmark for a thematically grouped region.
| Import | from hedron import Section |
| Distribution | hedron |
| Backend activity | No |
| Normal render mode | RenderMode.FRAGMENT |
Live demo¶
Render the semantic `section` landmark for a thematically grouped region.
The preview is a local docs simulation (not a running Hedron server). Interactive demos show a “Simulated HTMX” trace when applicable.
Basic use¶
from hedron import Heading, Section, Text
component = Section(Heading('Recent activity', level=2), Text('Three deployments succeeded'))
Compose under Page for full documents, or return from a fragment route for HTMX swaps.
How it works¶
Section emits a native <section>, preserving semantic navigation instead of using a generic div. Children may be passed individually or as one non-string sequence. Landmark helpers are real typed classes with an allowlisted attribute set.
This component's core behavior is server-rendered HTML and does not require a browser runtime. The preview is ordinary semantic HTML, so keyboard, form, link, and disclosure behavior comes from the platform.
Constructor and parameters¶
Section(*nodes, children=None, class_=None, id=None, lang=None, dir=None, role=None, aria=None, data=None, ...)
| Parameter | Type | Meaning |
|---|---|---|
nodes |
NodeLike |
Positional content belonging to this semantic region. |
children |
NodeLike | sequence | None |
Keyword alternative; combines with positional nodes. |
class_ |
str | None |
Optional authored class name. |
id |
str | None |
Stable fragment or target identifier. |
lang / dir / role / title / tabindex / aria / data / hidden |
allowlisted |
Safe HTML attributes; hostile roles like presentation / none are rejected. |
Composition and backend behavior¶
Keep Section at the smallest semantic boundary. Fragment routes should return only
the replaced region and preserve stable target IDs across success, validation, empty,
loading, and error responses.
Section is primarily presentational; keep any mutation on an explicit action or component route.
Accessibility¶
Every significant section should have a heading that gives the region an accessible name.
Security¶
Escaping and SafeUrl / TrustedHtml are framework concerns; authorization and data
exposure remain application code. Redact secrets before rendering.
Common mistakes¶
- If the content has no meaningful heading, a generic container may be more appropriate.
- Do not copy docs-preview JavaScript into an application server.