Skip to content

Conversation

@marcel-rbro
Copy link
Contributor

@marcel-rbro marcel-rbro commented Jan 21, 2026

Summary

  • Enhanced the template property description in the output schema documentation
  • Added a new "Understanding templates" section that explains how templates work
  • Improved documentation flow from definitions → variables → understanding → examples

Changes

1. Enhanced Property Description

Updated the template property description in the "Output object definition" table to include:

  • Clear explanation of what templates do (generate output links)
  • Mention of Mustache-style {{variable}} syntax
  • Where generated URLs appear (Console Output tab and API response)

2. New "Understanding Templates" Section

Added a comprehensive section between "Available template variables" and "Examples" that covers:

  • How the Apify platform processes templates (variable interpolation, URL generation, display)
  • Template syntax with concrete examples showing before/after transformations
  • Where templates appear (Apify Console and API Response)
  • Smooth transition to the examples section

Context

Addresses feedback from GitHub issue #2165 where users requested better explanation of the template property.

The enhancement maintains brevity while providing essential information that helps users understand template mechanics before seeing practical examples.

Related

Test Plan

  • Build documentation locally to verify no syntax errors
  • Verify markdown rendering displays correctly
  • Confirm logical flow: Definitions → Variables → Understanding → Examples
  • Check that all code examples remain valid

🤖 Generated with Claude Code


Note

Improves the output schema docs to better explain how URL templates work.

  • Updates template property description to note Mustache {{variable}} syntax and where generated URLs surface (Console Output tab and API output)
  • Adds Understanding templates section covering interpolation, URL generation, display, and basic examples
  • Refines doc flow from definitions → variables → understanding → examples in sources/platform/actors/development/actor_definition/output_schema/index.md

Written by Cursor Bugbot for commit b6ce3dd. Configure here.

Improve the documentation for the `template` property in output schemas
by expanding the property description and adding a comprehensive
"Understanding templates" section that explains template processing,
syntax, and where generated URLs appear.

Changes:
- Enhanced template property description with Mustache syntax details
- Added "Understanding templates" section explaining:
  - How the platform processes templates (interpolation, generation, display)
  - Template syntax with concrete examples
  - Where templates appear (Console and API)

Addresses feedback from GitHub issue #2165.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@marcel-rbro marcel-rbro requested a review from TC-MO as a code owner January 21, 2026 13:22
@github-actions github-actions bot added the t-docs Issues owned by technical writing team. label Jan 21, 2026
marcel-rbro and others added 2 commits January 21, 2026 14:26
Fix bold usage to comply with Apify style guide by:
- Remove bold from list items used for emphasis
- Apply bold only to UI elements (Output tab)
- Fix Apify Console terminology (remove "the")

Following APIFY_STANDARDS.md text formatting standards where bold
is used exclusively for UI elements, not for emphasis.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Change "Understanding templates" to "Understand templates" to follow
Apify style guide requirement for simple present tense headings.
Avoid gerund (-ing) forms in headings per APIFY_STANDARDS.md.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Remove "Mustache-style" from template syntax description
- Lowercase "API Response" to "API response" for consistency

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants