How to get a forum for you or your company
The purpose of this forum is to provide a place where developers can post announcements and documentation about their plugins and where they can provide support for their users. When a developer wants to create this presence, send an email to developer-relations AT perceptiveautomation DOT com to request that we create a sub-forum for you (or your company). Provide the name of the forum (your name or company perhaps) and an optional one sentence blurb about you, your company, and/or your plugins. We'll create the forum and give you full access. You can post sticky posts, announcements, polls, etc. here to help support your customers. You can use URLs pointing to various topics in your area in the various URL fields in your plugin. This area will fundamentally replace the User Contribution
area for plugin developers - that section can remain for sharing scripts, images, apps, etc. (and the File Library
will remain for those types of items). If you already have topics in that forum that you would like to be moved to your new sub-forum, let us know and we'll move them for you.
Your sub-forum is there to use as you wish. However, we have some recommendations: post documentation for each of your plugins as sticky topics so it always floats to the top of the "Topics" list. You can post version announcements as announcements which will show up in an "Announcements" section, above the "Topics" list. So, when a user enters your forum, they'll see Announcements first in reverse chronological order, followed by the Topics section with your sticky posts (again, in reverse chronological order) the followed by normal posts by you and your users. FYI - you also can "lock" topics that you don't want users posting to - first, create and save the topic then edit it and click the "Lock Topic" button. You can unlock it temporarily if you want to post a reply to the topic then lock it back.
One other hint about using sub-forums here - you can specify one as the help URL in your plugins but make sure to url encode the ampersand (&) in the URL.