Skip to content

design: help text for content fields - #4384

Open
Stormster wants to merge 1 commit into
emdash-cms:mainfrom
Stormster:design/content-field-help-text
Open

Stormster wants to merge 1 commit into
emdash-cms:mainfrom
Stormster:design/content-field-help-text

Conversation

@Stormster

Copy link
Copy Markdown
Contributor

Design proposal

Proposal: proposals/content-field-help-text.md

I run EmDash for a niche of sites, edited by normal people rather than developers. A content field has a label and nothing else, so any guidance ends up crammed into the label, like "Full text, a blank line between paragraphs". That is hard to scan, and a screen reader reads the whole thing as the field's name.

This proposes an optional helpText in a field's options (and on repeater sub-fields). The editor shows it as one line under the field and links it to the field, so screen readers read it as the field's description. Nothing new is stored, and a field without help looks exactly as it does today.

I have a working version with tests on EmDash 1.3.1 and main. Before and after, on the same form:

Before:

Alert edit form today: Severity, Title and date fields with only a label above each

After:

The same form with one line of help text under each field, such as: Pick Urgent for danger or a closure, and Advisory for anything else.

Proposal type

  • Feature plan
  • RFC
  • Amendment, supersession, or withdrawal

Related work

None that I found.

Readiness

  • The proposal identifies its author and, for an RFC, its champion and Maintainer sponsor
  • The proposal describes observable behavior, compatibility, failure handling, and verification in proportion to its risk
  • Conflicting accepted or pending proposals are reconciled in this pull request
  • This pull request contains no implementation code
  • The proposal status is accepted (check only when ready to merge)

AI assistance

  • This proposal used AI assistance — model/tool: Claude Code (Claude Opus 5.5)

@changeset-bot

changeset-bot Bot commented Oct 24, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7115c8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@danielmlr danielmlr added the design/feature-plan Feature plan: merges once one Maintainer other than the author approves label Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: signed design/feature-plan Feature plan: merges once one Maintainer other than the author approves review/needs-review No maintainer or bot review yet size/M type/design

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants