Skip to content

Remove em dashes from the manifest and meta description - #14

Merged
vpetersson-bot merged 1 commit into
Screenly-Labs:masterfrom
vpetersson-bot:copy/remove-em-dashes
Aug 5, 2026
Merged

Remove em dashes from the manifest and meta description#14
vpetersson-bot merged 1 commit into
Screenly-Labs:masterfrom
vpetersson-bot:copy/remove-em-dashes

Conversation

@vpetersson-bot

Copy link
Copy Markdown
Contributor

Why

signage-apps.com (Screenly-Labs/app-store) fetches this app's .well-known/signage-app.json at build time and renders its description and summary directly onto the store pages. So em dashes in this manifest become em dashes on /, /examples/ and /timer/ over there, which is against the house copy style.

This was the one remaining source of em dashes on the store after Screenly-Labs/app-store#53; it could not be fixed from that repo because the manifest is fetched from this origin.

What changed

Copy only, three strings:

  • description: …once it passes — so the same screen… becomes …once it passes, so the same screen…
  • summary: Count down to — or up from — any moment. becomes Count down to or up from any moment.
  • index.html meta description: em dash becomes a colon

No schema, settings, launch template or behaviour change.

Verification

bun run typecheck, bun run lint, bun test (28 pass) and bun run build all clean. Built dist/.well-known/signage-app.json is valid JSON and both it and dist/index.html contain zero em dashes.

Note the store will keep serving the old text until this is deployed and the app-store rebuilds.

The app-store fetches this manifest at build time and renders its
description and summary straight onto signage-apps.com, so em dashes here
show up as em dashes on the store pages (/, /examples/, /timer/).

Rewrites the two manifest strings and the page meta description without
them. Copy only; no schema, settings or behaviour change.
@vpetersson-bot
vpetersson-bot merged commit 688d187 into Screenly-Labs:master Aug 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant