User Story
As a developer (human or AI agent) implementing pages with the Solid Design System, I would like a ready-made footer template composed of existing sd-* components, as well as documented guidance on the structure, content groupings, and responsive behavior Union Investment footers follow, so that I can implement a consistent, on-brand footer without guessing at layout, spacing, or missing required legal/navigation elements, and the design system covers common page chrome end-to-end (header and footer) instead of leaving footer as an unspecified gap.
Suggested Solution
Add a footer entry to the templates library, following the same pattern already established by header-navigation (a documented composition of existing components + guidance.
Should cover:
- Structure: logo/brand area, multi-column navigation link groups, legal/compliance row (Impressum, Datenschutz, AGB, Cookie-Einstellungen), optional social/contact icons row, optional newsletter/contact CTA slot.
- Composition: which existing components to reuse
- Responsive behavior: how columns stack/collapse on mobile (e.g. accordion-style grouping vs. flat stacked list — needs a decision, similar to the header's drawer pattern).
- At least one real/representative example using actual Union Investment footer content categories, not lorem ipsum, so it reads as a source of truth rather than a generic pattern.
Cross-reference: this closes the same kind of discovery gap flagged in [MCP components tool discoverability ticket] — right now an agent querying templates has no footer entry to find at all, regardless of how well components are described.
DoR
DoD
User Story
As a developer (human or AI agent) implementing pages with the Solid Design System, I would like a ready-made footer template composed of existing sd-* components, as well as documented guidance on the structure, content groupings, and responsive behavior Union Investment footers follow, so that I can implement a consistent, on-brand footer without guessing at layout, spacing, or missing required legal/navigation elements, and the design system covers common page chrome end-to-end (header and footer) instead of leaving footer as an unspecified gap.
Suggested Solution
Add a footer entry to the templates library, following the same pattern already established by header-navigation (a documented composition of existing components + guidance.
Should cover:
Cross-reference: this closes the same kind of discovery gap flagged in [MCP components tool discoverability ticket] — right now an agent querying templates has no footer entry to find at all, regardless of how well components are described.
DoR
DoD