. Our Public API users are using extensively this features to store configuration information standard easily readable by Heading - Name the feature in a way the reader (our target customers) will understand. Sub-Heading - Describe for who the feature is and what benefit the customer get from it. (One sentence only underneath the title.) Summary - Give a summary of the product and the benefit. Assume the reader will not read anything else so make this paragraph good. Problem - Describe the problem your product solves. (One sentence) Solution - Describe how your product elegantly solves the problem. (One sentence) How to Get Started - Describe how easy it is to get started or point to a How to page that can get access from the tutorial section. Other Call to Action (optional) - Give pointers where the reader should go next or if there are other feature related to the one you have described
Page Comparison
General
Content
Integrations