As a Community Manager, one of the repetitive tasks I have is writing product documentation. Making sure my community knows how to use the product I work on is a pretty important task, and even more important is making sure that you don't have to worry about keeping multiple copies of your documentation up to date.
We use a help desk and support platform called Zendesk. I write all of our community support documentation there, but to keep things pretty, I use Repost.Us to make the articles embeddable. Since our tutorials and help desk are Repost.Us enabled, this means that I have a single place to update documentation, and I don't have to worry about updating multiple pages. Another great thing this does is allow anyone to take the help documents I've written and post them to their sites. One thing I hate to worry about is blogs and media outlets covering the product I work for and citing documentation that becomes old when features are added. Now that you know why this is a good idea, let me show you how I do it.
Step 2: Set your help desk up with Repost.Us Site information & Selectors
Add your basic site information about your support desk.
Don't forget to add the CSS selectors! We use a very basic style for our help desk and don't have any customised CSS selectors. These may work for you: h3.entry-title for the Article Title and .user_formatted for the Article Body.
Step 4: Write your article and add the button code to it.
Step 5: Publish your article and repeat! You're going to need to add a button to every article, which is why I just paste the button script from step 4 at the very top of all of my articles. I can copy and paste them again into a new article easily without having to go back to Repost.Us every time.