Community Forum guidelines

Welcome to the Root Community Forum, for all developers building product modules on Workbench or integrating with the Root API. Here you can ask questions to the Root community, get answers and solution the future of insurance together. Get involved!

Please follow these guidelines when posting or answering questions on the Root Community Forum:

Choose your display name purposefully

• Choose a display name you are comfortable to expose to the public.
• Post using the same name and email address every time you use the forum.
• Use your correct email address. It is not visible to the public.

Don’t post sensitive information

• Your question should not include any sensitive information
• Make your question and examples generic

Do research before posting

• Search the Developer Hub for specific keywords related to your question
• Search the web if the problem you are facing is not specific to the Root platform
• Include links to useful resources that might help users to answer your question

Write a title that summarizes the specific problem

• Sum up your problem into one sentence
• Use correct grammar and spelling
• If you are struggling to summarize your question, do it last

Examples:

• Bad: Billing Day Confusion
• Good: How can I update the policy billing day via the API?

Introduce the problem before you post any code

In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself.

Help others reproduce the problem

Not all questions benefit from including code, but if your problem is with code you've written, you should include some. But don't just copy in your entire program! Not only is this likely to get you in trouble if you're posting your employer's code, it likely includes a lot of irrelevant details that readers will need to ignore when trying to reproduce the problem.

Proof-read before posting

Now that you're ready to ask your question, take a deep breath and read through it from start to finish. Pretend you're seeing it for the first time: does it make sense? Try reproducing the problem yourself, in a fresh environment and make sure you can do so using only the information included in your question. Add any details you missed and read through it again. Now is a good time to make sure that your title still describes the problem!

Stay true to the purpose of the Root Community Forum

The Root Community Forum is aimed at developers building on and integrating with Root. Please note that questions irrelevant to this cause will not be answered in this forum.

This guide is based on the guide to asking good questions on Stackoverflow.