Recipes for App Builder work best if readers can discover them and can tell quickly if this recipe solves their problem. Start with a summary so that readers can tell quickly what the recipe is about. If you were publishing this recipe to the Zendesk App Marketplace, this is the quick blurb to get readers to read on. A recipe does not need all these sections to be helpful to other app builders. You can write a Problem Statement and a Prompt and have enough to help people make a similar app.
Make sure to give your recipe a clear title, since that's going to be prominently displayed and found in searches. start with “Recipe: ”, then something helpful like the title of the app or the purpose, then “app” or “application”. Making your recipe easy to find helps everyone.
Problem Statement
What is the problem being addressed? This lets readers know if this recipe will solve their problem exactly or if it will need to be tweaked.
Potential Enhancements
This optional section provides guidance on additional features that are not in the prompt, but might make the resultant app more flexible or enhance the functionality.
Screenshots
This optional section can show the app as built. It can help uses determine if the app will resolve their issues. Tip:Use the caption feature to add a description of the images and the alt text button to help your recipe be accessible to all users.
Prompt
This very important section is what most people will be looking for. Prompts that follow the prompting guidelines work well here. Single prompt apps are preferred, but you can also discuss iterative prompts highlighting what was needed to get the application built.
Blueprint
This optional section can be used to copy the blueprint.md file from your project to give a more in-depth technical discussion of how the app was constructed. It's not necessary but can be very helpful for technically challenging apps.
Designer's Notes
This optional section is useful for any commentary on the app that you want to provide.