Authoring pains workshop
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
This is a bit of a placeholder issue. On the BCD calls we routinely end up talking about possible solutions to various authoring frustrations. We ought to have a session where we talk about our biggest problems with maintaining BCD, separately of proposed solutions, to find out where we might have shared problems or where solutions might resolve multiple problems at once.
Some issues that relate to this:
Contributor 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.
Research direction
Start by reading the related issue #20619 and reviewing the authoring frustrations raised during BCD calls. Done means organizing the proposed session separately from solution discussions and capturing shared maintenance problems or opportunities for solutions to address multiple problems.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100