Improvement to Plugin messaging on dev documentation:
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by locating the existing Plugin messaging documentation and its Bungeecord channel guidance. Update that documentation to explain creating personal channels, and consider the work done when users can follow the guidance for cases that do not use Bungeecord's channel.
Written by the indexing model from the issue text.
Description
Now we can create our own channel instead of using Bungeecord's, so implementing it in the docs is necessary for cases with personal channels.
- Dominant language
- MDX
- Stars
- 73
- Forks
- 280
- Avg merge
- 16h 42m
- Merged PRs (30d)
- 5
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.
More from PaperMC/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
dev guide project: Paper
Similar issues
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Link Checker Report Openautomated issue report
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
VoltAgent/awesome-design-md#469 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
KhronosGroup/glTF#2648 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
sccn/sccn.github.io#108 ·