Skip to content

fix(walkthrough): end the tour on a call to action that opens the docs - #724

Merged
rubenvdlinde merged 2 commits into
developmentfrom
fix/walkthrough-docs-cta
Aug 24, 2026
Merged

fix(walkthrough): end the tour on a call to action that opens the docs#724
rubenvdlinde merged 2 commits into
developmentfrom
fix/walkthrough-docs-cta

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

The guided tour's final step had no task, so it stopped without telling the user where to go next. It now closes on the documentation, per the fleet rule that a walkthrough's last step points somewhere.

The CTA targets the Documentation nav item that already exists in this app's menu, so it lands on a real destination rather than a URL invented for the copy. I checked the URL resolves (HTTP 200) before pointing users at it.

The same step carried voice defects

Measured against the shared writing skill (ConductionNL/hydra#610):

Was Why it fails
Nicely done praise, not voice
em-dash, stripped fleet-wide
reopen this tour anytime from the … menu housekeeping in the one line a user is most likely to act on

The title now states what the user actually has; the body says what to do with it. No em-dashes, every sentence under 16 words, the task starts with a verb.

Verification

JSON parses, the final step has a task, and its target resolves to a Documentation menu entry that exists in this manifest. CI's manifest-validation gate covers the schema.

Part of a fleet sweep across the 9 apps that ship a walkthrough. The survey read each manifest from origin/development, not from local working trees, because those sit on other sessions' branches and give a wrong answer.

The final step had no `task`, so the guided tour stopped without telling the
user where to go next. It now closes on the documentation, per the fleet rule
that a walkthrough's last step points somewhere.

The CTA targets the `Documentation` nav item that already exists in this
app's menu, so it lands on a real destination rather than a URL invented for
the copy.

The same step also carried voice defects the shared writing skill bans:
"Nicely done" is praise rather than voice, the em-dash is stripped
fleet-wide, and "reopen this tour anytime from the … menu" is housekeeping in
the one line a user is most likely to act on. The title now states what the
user actually has, and the body says what to do with it.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/stackiq @ 993036d

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
check-vue-demi
test-l10n
format
check-schema-l10n
composer ✅ 130/130
npm ✅ 720/720
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman ⏭️
Playwright
Hydra gates

Quality workflow — 2026-08-24 09:48 UTC

Download the full PDF report from the workflow artifacts.

development renamed the create-organisatie step's register from
`voorzieningen` to `stackiq`; this branch rewrote the final step to end on a
call to action. Both are correct and neither supersedes the other, so the
resolution takes development's register and this branch's final step.

Also removed the em-dash from the create-organisatie body while resolving.
It is the same voice defect this branch exists to fix, sitting two lines
above the step being fixed, and leaving it would have shipped a PR that
strips an em-dash from one step and steps over one in its neighbour.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/stackiq @ ecb251f

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
check-vue-demi
test-l10n
format
check-schema-l10n
composer ✅ 130/130
npm ✅ 720/720
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman ⏭️
Playwright
Hydra gates

Quality workflow — 2026-08-24 10:58 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit 9feb3c2 into development Aug 24, 2026
83 checks passed
@rubenvdlinde
rubenvdlinde deleted the fix/walkthrough-docs-cta branch August 24, 2026 15:50
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