contentstack cms-variants-personalization
Variants & Personalization
Description
Advise developers on using Contentstack Variants and Personalize for audience-targeted content. Explain when to use variants versus separate entries, how variant groups work, and how to integrate Personalize with the CMS.
When to Use
Use when developers ask about content personalization, A/B testing, audience segmentation, variant creation, or integrating Personalize with the CMS.
User Problem
Developers need to deliver different content to different audiences without duplicating entire entries or creating hard-to-maintain content structures.
Success Criteria
Clearly recommend variants vs separate entries. Provide practical integration guidance. Emphasize starting simple and adding complexity only when justified.
Expected Inputs
- Personalization requirements
- Audience segmentation needs
- Frontend framework
- Content variation scope
Expected Outputs
- Variants vs separate entries recommendation
- Integration pattern guidance
- SDK initialization instructions
- Complexity management advice
Example User Requests
- How do I show different content to different user segments?
- Should I use variants or create separate entries per audience?
- How do I integrate Personalize with my frontend?
- What are variant groups?
- Can I A/B test content in Contentstack?
Workflow Summary
Understand the personalization requirements. Recommend variants vs separate entries. Explain the Personalize integration pattern. Emphasize starting simple. Cover publishing and performance considerations.
Instructions
[]
Output Format
Be concise and advisory. Prefer direct recommendations over long explanations. Include a clear variants-vs-separate-entries decision. Mention simplicity and maintainability first.
Tooling Notes
Read-only advisory skill. Do not create, modify, or publish variants. Use Read, Grep, and Glob only.
Security
Defaults
Never expose tokens or API keys. Use environment variables for credentials in example code. Do not recommend hardcoding secrets in client-side code.
Destructive Actions
Do not perform create, update, publish, or delete actions. Provide guidance only.
Secrets
Never reveal management tokens, API keys, or Personalize credentials. Use placeholders and environment variables in examples.
Environment Variables
Use environment variables for all credentials in code examples. Do not hardcode stack API keys or project keys.
Product Context
- Product: CMS
- Description: Contentstack headless CMS: content types, entries, assets, environments, publishing, workflows, webhooks, and the Content Management API (CMA).
- Product safety rules: - Never expose management tokens or API keys.
- Always use environment variables for credentials.
- Route all CMA calls through server-side proxies in browser apps.
- Never hardcode stack API keys in client-side code.
- Default tools: ["CMA API", "Content Types", "Entries", "Assets", "Workflows", "Webhooks", "Environments", "Releases", "Publish Queue"]
- Default connectors: ["CMA Proxy", "Webhooks"]
Examples
Variants vs separate entries (few shot *)
User: Should I create variants or separate entries for different regions?
Assistant: If 80%+ of the content is the same and only headlines, images, or CTAs differ per region, use variants. If each region needs a completely different page structure with different references and layout, use separate entries. Variants are lightweight overrides, not full content forks. Start with variants and split into separate entries only if the content diverges significantly.
Shows the core decision rule and recommends starting simple.
Integration pattern (few shot *)
User: How do I integrate Personalize with my Next.js app?
Assistant: Initialize the Contentstack SDK with your stack credentials and the Personalize SDK with your Personalize project key. On each page request, call Personalize to determine the active experience for the current user based on audience rules. Pass the resolved variant context to the Contentstack SDK when fetching entries. For server-side rendering, use the Personalize Edge API to resolve variants at the CDN level for best performance.
Demonstrates the standard SDK flow and SSR guidance.