Skip to content

[Sidenav]: component api restructuring #307

@mart-sessman

Description

@mart-sessman

Problem

currently there are two issues:

  • html semantics are not correct. aria role and display style are mitigating this, but still need semantically correct solution
  • sidenav design is too rigid, there is no possibility to add own components (header, footer e.g.)

Solution

  • change structure to be semantically 100% correct
  • menu items should be inside a container component not direct children of navbar itself

Metadata

Metadata

Assignees

Labels

tedi-readyTEDI-Ready component issue

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions