Documentation
Rider AI.
The conversational agent that edits your generated pages through natural language commands.
Overview
How Rider works.
Rider AI is a post-generation editing agent. After Gallop creates your page, Rider lets you refine it conversationally — without touching code or re-running the full pipeline.
Under the hood, Rider maintains a context window that includes the full page schema, your edit history, and the original prompt. This means every instruction is interpreted in the context of your entire page, not just a single element.
- Schema-aware: Rider knows every element type, property, and nesting constraint.
- Multi-turn: Edits are cumulative. Say "make the heading bigger" and then "actually, make it blue too" — Rider remembers.
- Non-destructive: Every edit creates a revision. Roll back to any previous state instantly.
// Rider's context per edit
{
"page": { ... }, // Full schema
"history": [ // Previous edits
"Added hero section",
"Changed heading color"
],
"prompt": "dental clinic",
"editRequest": "Make the CTA
button bigger and change
the text to Book Now"
}Capabilities
What Rider can do.
Edit content
Rewrite headlines, adjust body copy, change CTA text, update meta descriptions. Rider understands the full page context, so you can say "make the tone more casual" and it applies everywhere.
Restructure layouts
Move sections up or down, add new rows, change column widths, swap element positions. Describe the structural change in plain English.
Restyle elements
Change colors, font sizes, spacing, backgrounds, and borders. Rider maps your request to valid Stride CSS classes. No raw CSS needed.
Add new sections
Say "add a testimonial section after the services grid" and Rider inserts a fully structured section with placeholder content ready to edit.
Remove elements
Delete individual elements, entire sections, or specific columns. Rider handles cleanup — orphaned containers are automatically removed.
Translate content
Translate the entire page or specific sections into any supported language. Layout and styling are preserved. Schema constraints prevent hallucination.
Examples
Example commands.
Natural language instructions Rider understands. Be as specific or as general as you like.
Constraints
What Rider can't do.
Rider is powerful but intentionally constrained. These limits ensure generated pages are always production-ready WordPress content.
No custom JavaScript
Rider generates WordPress blocks with Stride CSS classes. It cannot inject arbitrary JavaScript, custom scripts, or external widget embeds.
Schema-bound elements
Every element Rider creates must conform to the Gallop element schema. It can't invent new element types or use properties that don't exist in the schema.
No external data
Rider works with the content on your page. It doesn't fetch external data, query APIs, or import content from other sites. All content is generated or user-provided.
Single page scope
Rider edits one page at a time. It can't make cross-page changes, update global settings, or modify your theme. Each editing session is scoped to a single page.
Best Practices
Tips for better results.
Be specific about scope
Instead of "make it look better," say "increase the heading font size in the hero section and add more padding between sections." Specificity produces more predictable results.
Reference sections by name
Use descriptive references: "the pricing section," "the second testimonial," "the hero CTA button." Rider maps these to specific elements in the page schema.
Chain small edits
Multiple small, focused edits produce better results than a single complex instruction. Edit the layout first, then content, then styling.
Early Access
Meet the Rider.
Get early access when we ship.