Content Comparison

Content Comparison Step

The "Content Comparison" Step allows you to visually compare two pieces of HTML content and highlight the differences between them. This powerful functionality is especially useful for reviewing content changes, tracking edits, and ensuring quality control in your content workflows.

What is the Content Comparison Step?

The Content Comparison step enables you to compare an original version of HTML content with a modified version, clearly visualizing additions, deletions, and changes. This is particularly valuable when you need to:

• Review AI-suggested content changes

• Track edits made during a content review process

• Verify content updates before publishing

• Maintain quality control over content versions

How to Configure the Content Comparison Step

Configuring the step requires setting the parameters shown below:

[ SCREENSHOT OF CONTENT COMPARISON CONFIGURATION PANEL]

Original Content

Specify the original HTML content that will serve as the baseline for comparison. This can be:

• A direct HTML string

• The output from a previous step (using Liquid syntax)

• Content retrieved from your Knowledge Base or external source

Modified Content

Specify the modified or updated HTML content that will be compared against the original. Like the original content, this can be:

• A direct HTML string

• The output from a previous step (using Liquid syntax)

• Content retrieved from your Knowledge Base or external source

Title (Optional)

Provide a descriptive title for the comparison to make it easier to identify in your workflow.

Options

Configure how the comparison should be performed:

• Comparison Type: Choose between "Side-by-Side" or "Inline" comparison views

• Highlight Changes: Toggle whether to highlight changes with color coding

• Ignore Whitespace: Option to ignore whitespace differences in the comparison

[ SCREENSHOT OF COMPARISON OPTIONS]

Output

The Content Comparison step outputs a visual representation of the differences between the two HTML content versions. The output includes:

• Color-coded highlighting of additions (typically in green)

• Color-coded highlighting of deletions (typically in red)

• Visual indicators for modified sections

• The comparison in either side-by-side or inline format based on your configuration

Additionally, the step outputs a JSON object containing:

{
  "hasChanges": true,
  "changeCount": 5,
  "additions": 3,
  "deletions": 2,
  "htmlComparison": "<div class='comparison'>...</div>"
}

[ SCREENSHOT OF CONTENT COMPARISON OUTPUT]

How to Reference the Output

You can reference the output of the Content Comparison step in subsequent steps using Liquid syntax:

• To check if there are changes: {{ step_x.output.hasChanges }}

• To get the number of changes: {{ step_x.output.changeCount }}

• To use the HTML comparison: {{ step_x.output.htmlComparison }}

Common Use Cases

Content Review and Approval

Integrate the Content Comparison step with Human Review steps to allow reviewers to clearly see what changes have been made to content before approving it.

AI-Assisted Content Editing

Compare original content with AI-enhanced versions to visualize and evaluate AI-suggested improvements.

Content Quality Control

Implement content comparison as part of a quality control workflow to ensure that content updates maintain consistency with style guidelines and requirements.

Version Tracking

Track changes between different versions of the same content over time to maintain a record of how content has evolved.

Best Practices

1. Use with Human Review: Combine Content Comparison with Human Review steps to make the review process more efficient.

2. Structured HTML: Ensure your HTML is well-structured to make comparisons more accurate and easier to interpret.

3. Focus on Important Changes: Configure the comparison to ignore minor differences like whitespace when only substantive changes matter.

4. Provide Context: Include a descriptive title and clear labeling to help reviewers understand what they're comparing.

5. Consider Output Format: Choose between side-by-side and inline comparisons based on the nature of your content and what's easier for reviewers to understand.

Integration with Other Steps

The Content Comparison step works particularly well when combined with:

• Human Review Steps: To facilitate informed decision-making about content changes

• LLM Steps: To compare original content with AI-generated or AI-enhanced versions

• Write to Grid Steps: To store comparison results for future reference

• Conditional Steps: To create different workflow paths based on whether changes were detected