Interface texts: start every sentence and label with a capital, and end every sentence with a full stop

Open
  • Is something wrong?
#693 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@guidol-ive is already working on this.

Since Oct 29, 2026.

  • #694 by @guidol-ive — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
internationalization

Research direction

Review the earlier single-text issues #652, #654, and #658, then inspect the interface text locations they identify. Apply the proposed capitalization and punctuation rules consistently to labels, sentences, and text fragments, preserving intentional lowercase fragments and continuations. The issue gives no test or file names; done means the listed rules are applied across interface texts, and linked pull request #694 indicates work is already underway.

Written by the indexing model from the issue text.

Description

Component: User interface Impact: Low Level: Easy Type: Enhancement Value: Users Value: Visitors

Many texts of the interface start with a lower-case letter, and many sentences have no end mark, for example:

  • het versturen van e-mail naar de volgende adressen is mislukt: (notification)
  • Deze pagina bestaat niet (notification)
  • voeg reactie toe, opmerkingen (button and heading below an article)

Some buttons look right only because a theme sets text-transform: uppercase; in other themes, in the mail and in screen readers the lower case shows.

House rule proposed:

  • Every label (button, field label, heading, option, menu item, mail subject) starts with a capital and has no end mark.
  • Every sentence (notification, help text, mail body) starts with a capital and ends with ., ? or !.
  • A word or phrase that the code puts inside another text keeps its lower case (door, dagen, uitgenodigd), and a text the code continues (ending in : or a space) keeps its ending.

Earlier issues about single texts: #652, #654, #658.

🤖 Generated with Claude Code

Dominant language
JavaScript
Stars
5
Forks
9
Avg merge
18h 49m
Merged PRs (30d)
13

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from PlanBCode/hypha

All issues in PlanBCode/hypha

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.