RSSNext / RSSNext/Folo

let text wrap instead of using end-of-line word-breaks

Open
#4,339 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
39k
Forks
2.1k
Avg merge
1d 4h
Merged PRs (30d)
10

Description

Clear and concise description of the problem

End-of-line word-breaks should be used sparingly. It can reduce the readability if used too much. Most of the content in the digital world just let the text wrap instead of breaking words. We should follow that convention.

Suggested solution

I suggest turn off word breaking for content page but leave it on for descriptions where space efficiency is more important.

Example content
Word breaking on (current) Word breaking off (suggested)
Image Image

It's much more natural to see the typesetting on the right.

Example description
Word breaking on (current, keep it) Word breaking off
Image Image

IMO it's ok to break words in the description of the feed as we need the space.

Validations

  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • This issue is valid

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the content-page and feed-description rendering or styling in the TypeScript frontend, then compare the examples; done when content pages wrap naturally while descriptions retain word breaking.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.