Skip to content

Commit 62b3c9d

Browse files
committed
Improved diagrams
1 parent f43468e commit 62b3c9d

4 files changed

Lines changed: 28 additions & 35 deletions

File tree

docs/guides/use-cases/data-processing-etl.mdx

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,17 +34,11 @@ Build data pipelines that process large datasets without timeouts. Handle stream
3434

3535
## Why Trigger.dev for data processing
3636

37-
**Process datasets for hours without timeouts**
37+
**Process datasets for hours without timeouts:** Handle multi-hour transformations, large file processing, or complete database exports. No execution time limits.
3838

39-
Handle multi-hour transformations, large file processing, or complete database exports. No execution time limits.
39+
**Parallel processing with built-in rate limiting:** Process thousands of records simultaneously while respecting API rate limits. Scale efficiently without overwhelming downstream services.
4040

41-
**Parallel processing with built-in rate limiting**
42-
43-
Process thousands of records simultaneously while respecting API rate limits. Scale efficiently without overwhelming downstream services.
44-
45-
**Stream progress to your users in real-time**
46-
47-
Show row-by-row processing status updating live in your dashboard. Users see exactly where processing is and how long remains.
41+
**Stream progress to your users in real-time:** Show row-by-row processing status updating live in your dashboard. Users see exactly where processing is and how long remains.
4842

4943
## Example workflows
5044

docs/guides/use-cases/marketing.mdx

Lines changed: 19 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Marketing workflows"
3-
sidebarTitle: "Marketing workflows"
3+
sidebarTitle: "Marketing"
44
description: "Learn how to use Trigger.dev for marketing workflows, including drip campaigns, behavioral triggers, personalization engines, and AI-powered content workflows"
55
---
66

@@ -38,17 +38,28 @@ Build marketing workflows from drip campaigns to real-time personalization. Hand
3838

3939
## Why Trigger.dev for marketing
4040

41-
**Delays without idle costs**
41+
**Delays without idle costs:** Wait hours or weeks between steps. Pay only for active compute, not wait time. Perfect for drip campaigns and scheduled follow-ups.
4242

43-
Wait hours or weeks between steps. Pay only for active compute, not wait time. Perfect for drip campaigns and scheduled follow-ups.
43+
**Guaranteed delivery:** Messages send exactly once, even after retries. Personalized content isn't regenerated on failure.
4444

45-
**Guaranteed delivery**
45+
**Scale without limits:** Process thousands in parallel while respecting rate limits. Send to entire segments without overwhelming APIs.
4646

47-
Messages send exactly once, even after retries. Personalized content isn't regenerated on failure.
47+
## Production use cases
4848

49-
**Scale without limits**
50-
51-
Process thousands in parallel while respecting rate limits. Send to entire segments without overwhelming APIs.
49+
<CardGroup cols={2}>
50+
<Card title="[Customer/Company Name]" icon="building">
51+
[1-2 sentence description of what they built and the impact/result]
52+
</Card>
53+
<Card title="[Customer/Company Name]" icon="building">
54+
[1-2 sentence description of what they built and the impact/result]
55+
</Card>
56+
<Card title="[Customer/Company Name]" icon="building">
57+
[1-2 sentence description of what they built and the impact/result]
58+
</Card>
59+
<Card title="[Customer/Company Name]" icon="building">
60+
[1-2 sentence description of what they built and the impact/result]
61+
</Card>
62+
</CardGroup>
5263

5364
## Example workflows
5465

docs/guides/use-cases/media-generation.mdx

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,17 +34,11 @@ Build AI media generation pipelines that handle unpredictable API latencies and
3434

3535
## Why Trigger.dev for AI media generation
3636

37-
**Pay only for active compute, not AI inference time**
37+
**Pay only for active compute, not AI inference time:** Checkpoint-resume pauses during AI API calls. Generate content that takes minutes or hours without paying for idle inference time.
3838

39-
Checkpoint-resume pauses during AI API calls. Generate content that takes minutes or hours without paying for idle inference time.
39+
**No timeout limits for long generations:** Handle generations that take minutes or hours without execution limits. Perfect for high-quality video synthesis and complex multi-modal workflows.
4040

41-
**No timeout limits for long generations**
42-
43-
Handle generations that take minutes or hours without execution limits. Perfect for high-quality video synthesis and complex multi-modal workflows.
44-
45-
**Human approval gates for brand safety**
46-
47-
Add review steps before publishing AI-generated content. Pause workflows for human approval using waitpoint tokens.
41+
**Human approval gates for brand safety:** Add review steps before publishing AI-generated content. Pause workflows for human approval using waitpoint tokens.
4842

4943
## Example workflows
5044

docs/guides/use-cases/media-processing.mdx

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,17 +34,11 @@ Build media processing pipelines that handle large files and long-running operat
3434

3535
## Why Trigger.dev for media processing
3636

37-
### Process multi-hour videos without timeouts
37+
**Process multi-hour videos without timeouts:** Transcode videos, extract frames, or run CPU-intensive operations for hours. No execution time limits.
3838

39-
Transcode videos, extract frames, or run CPU-intensive operations for hours. No execution time limits.
39+
**Stream progress to users in real-time:** Show processing status updating live in your UI. Users see exactly where encoding is and how long remains.
4040

41-
### Stream progress to users in real-time
42-
43-
Show processing status updating live in your UI. Users see exactly where encoding is and how long remains.
44-
45-
### Parallel processing with resource control
46-
47-
Process hundreds of files simultaneously with configurable concurrency limits. Control resource usage without overwhelming infrastructure.
41+
**Parallel processing with resource control:** Process hundreds of files simultaneously with configurable concurrency limits. Control resource usage without overwhelming infrastructure.
4842

4943
## Example workflows
5044

0 commit comments

Comments
 (0)