Inter-interface Navigation Component(s)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by auditing the repeated #projectManagementBtn HTML and CSS, then review the existing tpen-gui-action-link and related tpen-gui-* components. Identify the interfaces that link to /project/manage and the /project/options example. Done means a reusable navigation component supports multiple arbitrary outgoing links, including both listed destinations.
Written by the indexing model from the issue text.
Description
We have made every AI angry with #projectManagementBtn. It's a copy and pasted HTML + CSS solution across interfaces and components to navigate back to project management. It occurred because every edit-project-data related interface needs a link back into project-management-home so the user doesn't get lost.
We know this mechanic will be repeated here and in other places. We even planned for it with the tpen-gui-action-link and other components in the tpen-gui-* space. Maybe it is time to take a hard look at these navigational moments and make a decision for what to do when we need the same one or multiple across different interfaces and components.
Think hard about how to componentize the use of the buttons included in interfaces and components that link back to /project/manage.
Consider that this will be repeated for links into other interfaces and components as they are designed. Let this mechanic work for any link out, not just /project/manage.
The component could be used multiple times on the same page to handle multiple links out. For example, /project/options should have two - one to go to /project/transcribe and one to go /project/manage.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CenterForDigitalHumanities/TPEN-interfaces
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
License link borkedOpen
Difficulty 1/5 Under an hour Newbie friendliness 68/100
All issues in CenterForDigitalHumanities/TPEN-interfaces
Similar issues
-
Four problem loader browser tests fail on WindowsPossibly taken @Patriciaath999 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
juice-shop/juice-shop#3686 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
TheOdinProject/curriculum#31465 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TurboDocx/html-to-docx#254 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day