Rename section header on all pages in the solution index
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Open Resource 1.0.1 at docs/known-issues-and-solutions/solutions-index and review each page in the solution index. Find the Page Content Status bullet and the corresponding Project Team Error Guidance section, then update both names as specified, preserving any page-specific team name. Done means all relevant pages use the new Error Fix Example(s) from Project Teams wording and the changes are saved and committed.
Written by the indexing model from the issue text.
Description
Overview
We need to rename the TDM or Project Name Error guidance section to Error Fix Example(s) from Project Teams on all pages in the solution index so that there is a distinction between guidance and the actual fix used (shown by the examples)
Action Items
- Go to Resource 1.0.1.
- Open the page you want to update.
- Edit the page.
- Under
Page Content Status, rename the bulletProject Team Error GuidancetoError Fix Example(s) from Project Teams. - Find the
Project Team Error Guidancesection further down the page. - Rename it to
Error Fix Example(s) from Project Teams(orError Fix Example(s) from <Project> Teamif the page uses a specific team name). - Save and commit.
Resources/Instructions
- Dominant language
- No language data
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 hackforla/accessibility
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hackforla/accessibility#72 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hackforla/accessibility#68 · 3 comments ·
-
Add icons at the top of all pages in the solutions indexMay be free again @rayneng claimed this 63 days ago, and no pull request is open. Open
hackforla/accessibility#66 · 7 comments · 1 assignee ·
-
Create Issue templates for teams to be able to do an accessibility auditMay be free again @Rabia2219 claimed this 151 days ago, and no pull request is open. Open
hackforla/accessibility#32 · 17 comments · 1 assignee ·
All issues in hackforla/accessibility
Similar issues
-
Release notesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mieweb/timehuddle#634 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Add: EntuneOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AbdelStark/awesome-typesafe-jev#187 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
blinklabs-io/dingo#4937 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TheOdinProject/curriculum#31444 ·
Maintainers usually reply within 1 day