bullitt/trackbox

Fork 0

Settings: Simplify scraper toggle copy and make Notifications implementation-neutral #43

New issue

Closed

opened 2026-06-27 15:41:16 +02:00 by bullitt · 1 comment

bullitt commented

2026-06-27 15:41:16 +02:00

Owner

Problem

Two copy/labeling issues in Settings:

Each scraper card has a toggle labeled "Enable DHL Scraping" / "Enable HERMES Scraping" — but the card header already reads "DHL Web Scraper" with a status badge "Enabled". The toggle label repeats information already present in the header.
The Notifications card title reads "Notifications — Home Assistant MQTT". This mixes the feature name with the implementation detail. Users who see "Home Assistant MQTT" might think this only works with HA, when it could be any MQTT subscriber.

Implementation

File: frontend/src/pages/Settings.tsx

Fix 1 — Toggle label

Change:

<label className="text-sm font-medium">Enable {s.carrier.toUpperCase()} Scraping</label>

To:

<label className="text-sm font-medium">Enabled</label>

Fix 2 — MQTT card title

Change:

<CardTitle className="text-base">Notifications — Home Assistant MQTT</CardTitle>

To:

<CardTitle className="text-base">Notifications</CardTitle>

And add a CardDescription below it:

<CardDescription>Publish state changes via MQTT (e.g. Home Assistant auto-discovery)</CardDescription>

Acceptance criteria

Toggle label reads "Enabled" not "Enable DHL Scraping"
Notifications card title reads "Notifications"
MQTT implementation detail is in the description, not the title

Brand identity alignment

Settings copy should be precise and implementation-transparent. The UI should not overfit notifications to Home Assistant if the underlying mechanism is MQTT or webhook-style publication.

Brand-compliant implementation notes

Use Enabled for per-carrier scraper toggles because the card title already names the carrier/source.
Use Notifications as the card title, with implementation detail in description: Publish state changes via MQTT for automations such as Home Assistant.
Keep local/self-hosted framing subtle; avoid marketing copy.

Additional acceptance criteria

Copy is concise and non-redundant.
MQTT is explained as a composable integration, not a Home Assistant-only feature.
Toggle states are visually clear without repeated carrier names.

Migrated from GitHub issue #22: https://github.com/bullitt186/trackbox/issues/22
Original author: @bullitt186
Original created: 2026-06-27T13:25:30Z
Original labels: ux

## Problem Two copy/labeling issues in Settings: 1. Each scraper card has a toggle labeled "Enable DHL Scraping" / "Enable HERMES Scraping" — but the card header already reads "DHL Web Scraper" with a status badge "Enabled". The toggle label repeats information already present in the header. 2. The Notifications card title reads "Notifications — Home Assistant MQTT". This mixes the feature name with the implementation detail. Users who see "Home Assistant MQTT" might think this only works with HA, when it could be any MQTT subscriber. ## Implementation File: `frontend/src/pages/Settings.tsx` ### Fix 1 — Toggle label Change: ```tsx <label className="text-sm font-medium">Enable {s.carrier.toUpperCase()} Scraping</label> ``` To: ```tsx <label className="text-sm font-medium">Enabled</label> ``` ### Fix 2 — MQTT card title Change: ```tsx <CardTitle className="text-base">Notifications — Home Assistant MQTT</CardTitle> ``` To: ```tsx <CardTitle className="text-base">Notifications</CardTitle> ``` And add a `CardDescription` below it: ```tsx <CardDescription>Publish state changes via MQTT (e.g. Home Assistant auto-discovery)</CardDescription> ``` ## Acceptance criteria - Toggle label reads "Enabled" not "Enable DHL Scraping" - Notifications card title reads "Notifications" - MQTT implementation detail is in the description, not the title ## Brand identity alignment Settings copy should be precise and implementation-transparent. The UI should not overfit notifications to Home Assistant if the underlying mechanism is MQTT or webhook-style publication. ## Brand-compliant implementation notes - Use `Enabled` for per-carrier scraper toggles because the card title already names the carrier/source. - Use `Notifications` as the card title, with implementation detail in description: `Publish state changes via MQTT for automations such as Home Assistant`. - Keep local/self-hosted framing subtle; avoid marketing copy. ## Additional acceptance criteria - Copy is concise and non-redundant. - MQTT is explained as a composable integration, not a Home Assistant-only feature. - Toggle states are visually clear without repeated carrier names. --- Migrated from GitHub issue #22: https://github.com/bullitt186/trackbox/issues/22 Original author: @bullitt186 Original created: 2026-06-27T13:25:30Z Original labels: ux

bullitt added the

label

2026-06-27 15:41:16 +02:00

bullitt changed title from ~~Settings: Simplify per-carrier toggle label and fix MQTT section title~~ to Settings: Simplify scraper toggle copy and make Notifications implementation-neutral

2026-06-27 15:46:22 +02:00

bullitt commented

2026-06-27 16:03:20 +02:00

Author

Owner

Implemented in commit bd6b0e7. Toggle label changed from 'Enable {CARRIER} Scraping' to 'Enabled' — the carrier name is already in the card header, so the label was redundant. Notifications card title changed from 'Notifications — Home Assistant MQTT' to 'Notifications', with a CardDescription added: 'Publish state changes via MQTT (e.g. Home Assistant auto-discovery)'. MQTT is now framed as a composable integration rather than an HA-specific one.

Implemented in commit bd6b0e7. Toggle label changed from 'Enable {CARRIER} Scraping' to 'Enabled' — the carrier name is already in the card header, so the label was redundant. Notifications card title changed from 'Notifications — Home Assistant MQTT' to 'Notifications', with a CardDescription added: 'Publish state changes via MQTT (e.g. Home Assistant auto-discovery)'. MQTT is now framed as a composable integration rather than an HA-specific one.

bullitt closed this issue

2026-06-27 16:03:20 +02:00

No labels

arch

harness

security

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

bullitt/trackbox#43

No description provided.

Rows
Columns