Skip to content

docs(marketing): say which phases shipped and where each one stops - #1808

Merged
rubenvdlinde merged 1 commit into
developmentfrom
docs/marketing-programme-shipped
Sep 5, 2026
Merged

docs(marketing): say which phases shipped and where each one stops#1808
rubenvdlinde merged 1 commit into
developmentfrom
docs/marketing-programme-shipped

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

What

The marketing pages still read as a plan. All six phases are on development now, so the tables say so, and each row carries the limit that actually applies rather than an unqualified "Live":

  • Social publishing is provable on Mastodon alone until the LinkedIn, Meta and X developer applications are filed.
  • The keyword analysis needs a connected Search Console property; the watches and the Matomo reports need an OpenConnector source each.
  • The bookkeeping audiences need shillinq installed and a client linked to a shillinq organisation, and say so when they cannot answer.

Phase 2 is the row to read carefully. The content hub is live. Asking hermiq for a draft is not built, because nothing can write into Pipelinq as an agent yet, so the agent-authored mark has a renderer and no writer. Calling that phase "Live" would have been the kind of claim these pages exist to prevent.

The architecture page also records how the RFC 8058 headers reach the default transport, which phase 0 left open: the guarded private Message::getSymfonyEmail(), degrading with a logged warning where the mailer does not expose it. Verified against InstanceMailerTransport rather than restated from the plan.

Verification

cd docs && npm run build exit 0. npm run check:spec-links exit 0. No em-dashes in either page.

Worth knowing for the next person: a second docs build fails with Can't resolve '@site/build/…' because Docusaurus scans the previous build's own output. rm -rf docs/build first.

🤖 Generated with Claude Code

The pages still read as a plan. All six phases are on development now, so
the tables say so, and each row carries the limit that actually applies:
social publishing is provable on Mastodon alone until the developer
applications are filed, the keyword analysis needs a connected Search
Console property, and the bookkeeping audiences need shillinq and a client
linked to a shillinq organisation.

Phase 2 is the one to read carefully. The content hub is live; asking
hermiq for a draft is not built, because nothing can write into Pipelinq
as an agent yet, so the agent-authored mark has a renderer and no writer.

Also records how the RFC 8058 headers reach the default transport, which
phase 0 left open: the guarded private getSymfonyEmail(), degrading with a
logged warning where the mailer does not expose it.
@rubenvdlinde
rubenvdlinde merged commit 951e04d into development Sep 5, 2026
34 of 35 checks passed
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/pipelinq @ b10355b

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
check-l10n-js
composer ✅ 106/106
npm ✅ 637/637
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development
Hydra gates

Quality workflow — 2026-09-05 13:03 UTC

Download the full PDF report from the workflow artifacts.

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