[Request] Wrap markdown lines
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- markdown
- Domain
- content
Research direction
Review the repository's Markdown files and the linked Rust Gamedev Newsletter example first. Clarify the target wrap width and which files are in scope; done means the agreed Markdown content is consistently wrapped without unintended formatting changes.
Written by the indexing model from the issue text.
Description
Motivation
When editing markdown files, it's nice if they wrap at ~80 characters, so it's a bit more readable. We do this for the Rust Gamedev Newsletter (example).
It's quite subjective, but it does make it nicer for others to edit I think :)
- Dominant language
- HTML
- Stars
- 24
- Forks
- 68
- 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 SeaQL/seaql.github.io
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SeaQL/seaql.github.io#172 ·
-
help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
SeaQL/seaql.github.io#171 ·
-
help wanted
Difficulty 3/5 1-2 days Newbie friendliness 48/100
SeaQL/seaql.github.io#170 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
SeaQL/seaql.github.io#166 ·
-
Doc improvementsOpenhelp wanted
Difficulty 4/5 3-5 days Newbie friendliness 25/100
SeaQL/seaql.github.io#163 ·
All issues in SeaQL/seaql.github.io
Similar issues
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
erdos-status-sync
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
google-deepmind/formal-conjectures#7109 ·
Maintainers usually reply within 2 days
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 65/100
lingdojo/kana-dojo#32090 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
P2 UI/UX
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day