Skip to content

docs(temporal): draft the co-marketing blog post - #163

Open
dawidaksamski wants to merge 1 commit into
mainfrom
docs/WB-533-blog-post
Open

dawidaksamski wants to merge 1 commit into
mainfrom
docs/WB-533-blog-post

Conversation

@dawidaksamski

Copy link
Copy Markdown
Contributor

Temporal co-marketing blog draft

Draft of the guest post for temporal.io/blog, plus the screenshots it
uses and a shot list documenting how they were produced.

What's in it

  • docs/blog/temporal-co-marketing-draft.md: ~1,400 words in Temporal's
    partner-post pattern (developer problem, integration, Temporal UI
    screenshots). Bylined to Dawid, team voice.
  • docs/blog/temporal-co-marketing-shots.md: run metadata (workflow id,
    Temporal 1.29.3, UI 2.53.1, TS SDK 1.23.0, model endpoint, commit) and
    what each image shows.
  • Three PNGs from a single run, execution-a02ad048: the canvas after the
    run, the Compact Event History with the six node labels as Summaries,
    and the ActivityTaskScheduled detail for "Classify Ticket" showing the
    10 min / 2 attempt defaults. The hero is the canvas and history crops
    side by side; neither half is edited.

The argument

  1. Temporal solves reliability but ships nothing a product user can look
    at or change.
  2. In Workflow Builder the diagram is data. Rerouting is a save, not a
    deploy. In-flight runs keep the definition they started with.
  3. @workflowbuilder/temporal interprets the graph inside the Workflow:
    waves, one Activity per node, nextPort routing and pruning,
    errorPolicy, sequenced events. Executors and store stay yours.
  4. Events come back through the store port and the canvas paints the run.
  5. Labels as Summaries make Event History and the canvas read the same.

Review notes

  • The package is written up as already published on npm, per the
    decision to time the post to the release. The install line and the
    npm link will be dead until then.
  • Code snippets are trimmed copies of apps/execution-worker/.../worker.ts,
    workflows.ts, and the profile example in packages/temporal/README.md.
  • The claim that in-flight runs keep their definition rests on the graph
    travelling as workflow input, which the plugin README states.
  • No "no-code" / "low-code" phrasing, no partner-status claims, Keylane
    not named.

…shot

Add the draft for Temporal's co-marketing review under docs/blog, with
three screenshots from one real run of the Customer Support Triage
template on the reference stack and a shot list that records the run.

The post is written for Temporal's audience: durable execution has no
visual layer, the diagram is data the product user authors, the plugin
interprets it inside the Workflow, and the node labels reach Event
History as activity Summaries so the canvas and Temporal UI agree.
@dawidaksamski dawidaksamski self-assigned this Sep 18, 2026
@dawidaksamski
dawidaksamski marked this pull request as ready for review September 18, 2026 12:30
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.

2 participants