Community tips are detailed posts by Slate community members that share specific processes such as workflows, rules, application structure, and more and provide the community with problem solutions, unique ways to utilize features, and best or new practices.  

Community tips are the most-viewed part of the Slate community and help make the community the great resource it is. If you post a high-quality tip, we'll send you some swag, feature it in the Slatest News, and it may even turn into an article in the knowledge base! Sharing tips is a great way to build and demonstrate your expertise and publish your knowledge in a public forum.

Best practices for writing tips

Below are some general best practices for writing your tip:

• Break your tip into different sections. Dividing your tip into sections increases readability and prevents readers from skimming over text. The sample sections in this article provide ideas on how to break up your tip.

• Add headings to your sections. Headings give readers context to the section before they begin reading. To add headings

1. Select the text you want to make a heading.

2. Click the paragraph icon () at the top of the Details box.

3. Choose the appropriate heading level from the pick-list.

4. Your text will now be displayed as your selected heading.

• Title your post with a clear description of what your readers will learn—beginning with "Community Tip:" followed by verbs like "Creating" or statements like "How to" are good ways to capture readers' attention. Example,"Community Tip: How to group prompts in public-facing form fields"

• Link to documentation related to your tip. Including documentation can help guide readers with different levels of background knowledge.

• Include step-by-step instructions. Using numbered steps will make it easier for other users to implement your tip.

• Include screenshots. Screenshots help orient the reader and make it easier to follow along. They should not be larger than 600 pixels or smaller than 300 pixels. This is to accommodate the end-user layout.

Thank you so much for sharing your knowledge with the Slate Community!