Talk about your next project
RevenueCat content marketing

The lesson

Write each chapter card in a guide's table of contents as the chapter's conclusion, so the contents page works as a summary of the whole guide.

The move

The hero shows the title, the line 'In-app subscriptions without the boilerplate', a 'Start reading' button and a 'Download PDF' link next to a book-cover illustration. A table of contents groups chapters under headings such as Foundations, Client-side integration, Server-side and Production readiness. Each card gives a one-line claim, such as 'You don't need to build a verification server. RevenueCat already is your verification server.' A 'Prefer building from scratch?' box links to the Google Play Billing Handbook, followed by a 'What RevenueCat replaces' table that compares Raw Google Play Billing and With RevenueCat row by row.

Why it works

  • Our readChapter cards that state the result, such as subscription states resolving to one isActive check, let a developer see the whole argument without opening a chapter.
  • Our readGrouping chapters by stage, from Foundations through Production readiness to Reference, lets readers jump to the part of the build they are working on.
  • Our readThe 'You write' versus 'Handled internally' table turns the guide's case for the product into a list a reader can check line by line.

What not to copy

Don't copy RevenueCat's SDK claims or the specific Google Play Billing comparisons. Keep the takeaway-per-chapter contents, the link to a companion build-it-yourself guide, and the closing table of what you handle versus what the reader handles.

More from RevenueCat

More content marketing

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.