Allow the user to use the system font for the GUI.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
My friends who have dyslexia have expressed that they'd like to use the font that they use for the machines in the websites that they visit without braking them, although I must note that they don't particularly mind the one that Nextcloud currently provides. For me, this is problematic because I see no reason why Nextcloud should mandate its own font instead of the system/browser-provided one.
Describe the solution you'd like
(Allow the user to) use the browser-provided typeface, ideally by default.
Describe alternatives you've considered
Allow the user to choose the font from a combination box, of which 3 of the options are sans-serif, serif, and monospace, thereby allowing the user to use the browser-provided fonts for those standard aliases.
Additional context
https://help.nextcloud.com/t/85305/2?u=rokejulianlockhart isn't correct, at least for https://wim.nl.tab.digital.
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
The issue names no files, tests, or entry points. Start by locating the GUI typography styles and any existing font configuration, then determine where the browser-provided typeface can be enabled. Done means users can use the system or browser font as requested, with the behavior covered by an appropriate test or verification.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100