posit-dev / posit-dev/content-switcher
Post-implementation testing
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2
- Forks
- 1
- Avg merge
- 4m
- Merged PRs (30d)
- 2
Description
List of test items to run through after implementing on Workbench docs
- theme/styles (the background against default and dark theme)
- Accessibility
- headings in toc
- anchor links
- drop-down selector
- inline content
- blocks of content
- search
- kapa.ai
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the Workbench docs and running through each checklist item: theme styles, accessibility, headings, anchors, selectors, content blocks, search, and kapa.ai. Done means every listed area has been tested and its result recorded, but the issue does not name files, commands, or expected behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, documentation, testing
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100