Hypertune
  • Introduction
  • Getting Started
    • Set up Hypertune
    • Next.js (App Router) quickstart
    • Next.js (Pages Router) quickstart
    • React quickstart
    • Remix quickstart
    • Gatsby quickstart
    • Vue quickstart
    • Nuxt quickstart
    • Node.js quickstart
    • React Native quickstart
    • JavaScript quickstart
    • Python quickstart
    • Rust quickstart
    • Go quickstart
    • Web quickstart
    • GraphQL quickstart
  • Example apps
    • Next.js and Vercel example app
  • Concepts
    • Architecture
    • Project
    • Schema
    • Flag lifecycle
    • Logic
    • Variables
    • Splits
    • A/B tests
    • Staged rollouts
    • Multivariate tests
    • Machine learning loops
    • Events
    • Funnels
    • Hypertune Edge
    • Reduction
    • SDKs
    • GraphQL API
    • Git-style version control
    • App configuration
  • Use Cases
    • Feature flags and A/B testing
    • Landing page optimization
    • In-app content management
    • Pricing plan management
    • Permissions, rules and limits
    • Optimizing magic numbers
    • Backend configuration
    • Product analytics
  • Integrations
    • Vercel Edge Config integration
    • Google Analytics integration
    • Segment integration
    • Webhooks
      • Creating webhooks
      • Handling webhooks
  • SDK Reference
    • Installation
    • Type-safe client generation
    • Initialization
    • Build-time logic snapshot
    • Hard-coded fallbacks
    • Local-only, offline mode
    • Hydrate from your own server
    • Wait for server initialization
    • Provide targeting attributes
    • Local, synchronous evaluation
    • Remote logging
    • Getting flag updates
    • Serverless environments
    • Vercel Edge Config
    • Custom logging
    • Shutting down
Powered by GitBook
On this page
  1. Use Cases

In-app content management

PreviousLanding page optimizationNextPricing plan management

Last updated 1 year ago

You can use Hypertune as a headless CMS to manage, localize, personalize, A/B test and optimize in-app content like onboarding copy and checklists, guides and templates, tooltips and error messages, signup and upgrade flows, modals and banners, etc.

This lets you empower content, translation, marketing, product and customer success teams to update in-app content themselves.

Unlike a typical CMS, Hypertune lets you insert arbitrary logic for translation, personalization, A/B testing and machine learning. So you don't need to stitch together your CMS with your A/B testing platform and nontechnical marketers can A/B test new content quickly and easily, without needing help from developers.

To use Hypertune for in-app content management, follow the , but use String or custom types instead of Boolean, e.g. you might start with a schema like:

type Query {
  root(context: Context!): Root!
}

input Context {
  user: User!
}

input User {
  id: String!
  name: String!
  email: String!
}

type Root {
  pages: [Page!]!
}

type Page {
  title: String!
  content: [Block!]!
}

union Block = TextBlock | ImageBlock

type TextBlock {
  text: String!
}

type ImageBlock {
  imageUrl: String!
  height: Int!
  caption: String!
}

String formatting

You can format strings in Hypertune with arguments defined in your schema.

To create a formatted string, define an argument on the string field itself or one of its parent fields, e.g. in the Context. Then implement the string's logic with a Text Chain expression. Open the menu on the Text Chain to add an empty expression that you can set to an argument.

quickstart