patternfly / patternfly/patternfly-org

Navigation - Disabled vs Hide vs Empty state

Open
#3,922 1 comment 0 reactions 1 assignee View on GitHub

@mmenestr is already working on this.

Since Mar 18, 2024.

Content PF5
Dominant language
JavaScript
Stars
74
Forks
147
Avg merge
4d 11h
Merged PRs (30d)
2

Description

Would like to add more guidance around navigation, and what to do when someone shouldn't have access to it.
Describe that we do not recommend disabling the nav item - and we do not offer that option in PF, but we instead recommend either hiding it, or having an empty state once the user lands on the page, informing them why they can't access it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.