The Developer Community Blog is a place for community members to write and share blog posts about the interesting, fun, and unique ways in which they’re implementing SailPoint in their organizations.
How it Works
Before posting in the Community Blog category, you must post in the Blog Drafts category so that your blog can undergo review. This is also a great time to request feedback from other blog writers and SailPoint experts.
Getting access to the Blog Drafts category
- If you are an Ambassador or Expert Ambassador you will automatically be added to the blog draft category.
- If you are not an ambassador, you can request access to our Blog Writer group. Simply click the ‘Join’ button.
What should I write about?
Successful blog post submissions will be:
-
Original and Well Written: We want original work that hasn’t been published elsewhere and exhibits original thoughts and interesting points of view we can’t find anywhere else. This also means that the blog should not be entirely AI generated.
- While it is ok to use AI as a starting point or to polish something you’ve written, blogs that contain too much AI generated material will be rejected.
-
Code-driven: The result of your post should be something a reader can build upon. The code should be clearly explained and helpfully split up. Do not assume that readers have extensive knowledge of functionality. Include all necessary resources for completing the task, such as code, screenshots, templates, etc.
The audience for this blog will be developers and technical users of the SailPoint platform. In order to write a blog post that resonates with the developer community, we encourage you to focus on extensibility as your subject. Extensibility generally means anything that you can do that is not provided out-of-the-box in the user interface. This can include, but is not limited to, the following features of SailPoint:
- APIs
- Event Triggers
- Workflows
- Rules
- Transforms
- Web Service Connector
- SaaS Connector
- Beanshell scripts
- and more…
We encourage you to check out published blog posts to get an idea of the content we are looking for. You can also reach out to a member of the Developer Relations team with a summary of what you intend to write before you begin. This will help to ensure you are focusing on the right content that will resonate with the audience before you get to the review and publish phase.
Next Steps
Now that you have a solid draft of your blog, you can post it in the Blog Drafts category. Topics in this category must have one of the following tags to show which stage of the process it is in:
WIP(work in progress) - This tag means you are working on your blog draft and not actively seeking feedback.Feedback Requested– This tag means that you would like feedback from the community on your post. If there are specific things you would like feedback on please list them at the end of your post.Ready for Final Review– This tag means that you have taken in all the feedback received and edited your blog to a polished finished status. This tag will alert the Developer Relations team that there is a blog draft that needs a final review.
Timeline For Review
Once a topic is tagged with Ready for Final Review the DevRel team will review it within one week. If everything looks good we will post it in the Community Blog category on your behalf. If it needs revision we will contact you directly.
Ambassador Points
Community members will earn 250 points towards their Ambassador status for each published blog.