Welcome to the Evolve Payments API documentation — but this isn't just another static docs site.
This documentation site is a live demo of GitBook’s new adaptive content feature, where the content changes in real time based on who you are and what you need. You can explore how documentation adapts for four different user types — from new users, to enterprise teams, to prospective customers — by clicking one of the options below and viewing the docs through their lens.
Traditional documentation shows the same content to everyone, like a paper map displaying every possible route. GitBook's adaptive content is like GPS navigation — it knows where you are, understands your destination, and shows you exactly the right path to get there.
Instead of overwhelming every visitor with all possible information and hoping they find their way to the right place in your docs, adaptive content creates personalized documentation experiences tailored specifically for every one of your users.
This is a demonstration of GitBook's adaptive content feature using a fictional “Evolve Payments” API. The adaptive behaviors you see here represent real capabilities available in GitBook today.
Learn more:
Experience the future of documentation — where every user gets exactly what they need, when they need it.
New user
Isobel has just signed up for Evolve Payments, and is currently exploring the platform. She doesn’t know exactly where to get started, or what the full capabilities of the platform are.
Software engineer
Katy is an experienced developer at her company, and has been using Evolve Payments for a long time. She has been tasked with implementing Evolve Payments with her company’s Stripe instance.
Prospective customer
Harry has not yet signed up for Evolve Payments, but his company is in the market for a new payment provider to hook up with their Shopify instance.
Enterprise user
Jared is a long-term Evolve Payments user, and has just joined the Google enterprise team and has tasked Jared with setting up enterprise-only features.
Adapt site sections — like specific docs for enterprise or internal users.
Show specific content for users — like the products they have available to them or the plan they’re currently on.
Adapt your site regionally with language variants or a specific version of a product your users are using.
Show specific product docs for features your users have access to or the feature flags they have enabled.
Populate content with specific information from your users — like their developer keys or other product information.
Ask the GitBook assistant anything you need — and get answers using context from the user asking the question.
