Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#693 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@guidol-ive 已经在做这个了。

开始于 2026年10月29日。

  • #694 来自 @guidol-ive —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
JavaScript
星标
5
派生
9
平均合并
19 小时 10 分钟
30 天内合并 PR
12

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PlanBCode/hypha 的其他 Issue

查看 PlanBCode/hypha 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。