@jjdecker the developer community forum completely open and crawled by every major search provider, including Google! As we continue to have incredibly involved users like yourself, those search results will continue to rise to the top.
I have added your request for automatic dark/light mode to our backlog as well—that should be an easy change for us to make!
Our team is responsible only for the SailPoint Developer Community, but I will continue to share your all’s sentiments with the Compass team about opening up their platform as well.
I’m curious to hear the reasoning for auto-closing developer forum posts after 60 days. I’ll often encounter an older post while researching an issue and may have additional questions for the previous commenters or even a solution to share if the post had originally gone unsolved.
I feel that allowing the posts to stay open indefinitely (or close at the posters discretion) would streamline discussion on certain topics and reduce the number of duplicate posts.
Really great question! What we’ve found over the years is that responding to topics older than about 60-90 days, has a very low rate of return for the original poster (and/or the other commentors) to reply to the person reviving the conversation. At best, there’s a reply and a “we’re way past that problem now”.
What we’ve found works really well is closing the topic after 60 days, and all you have to do to revive the conversation is simply create a new topic and reference the old topic in your post, and just share the link so it unfurls like this:
We found that this has much higher rate of success for that person!