I've been searching for a decent and, most importantly, simple wiki solution now for the past few weeks. I needed something easy to use and manage for Snaggr's documentation. All of the potential software I found were either too bloated or too shithouse to use.

Maintaining documentation using a simple medium with a decent built-in search and suggest system is pretty important. Especially when it comes to writing pages upon pages of instructions and standards for something that's constantly changing and growing. I shouldn't have to think about how to use the software, I just want to fucking post shit and easily organize it.

Even though I'm on a pretty tight, self-imposed, deadline for the API, I actually took the some time off yesterday and began writing my own wiki solution on top of the Kohana framewok. Three hours into it I decided to take a small break and search around on the net for other APIs I could potentially integrate into Snaggr. I happened upon a nice little service named Ember.

According to Ember it's:

"... the best way to share your design inspiration with the world - from webpages to screenshots, design to illustration, Ember is built for creatives looking to build an online design scrapbook."

Ok.

Well, the screenshot and illustration part caught my attention and I quickly discovered they provide a simple API. Unfortunately, according to it's online documentation, it doesn't support text-based search, but that's besides the point of this post. I noticed that Ember's support documentation is externally hosted by another service; Tender Support.

Apparently, it's by the same guys who created Lighthouse, which is an issue tracking system I used to use. I really liked working with Lighthouse and figured if it's by the same guys, Tender Support must be alright as well. I signed up for the 30 trial and began working.

Tender pretty much has everything I need to get the documentation up and running quickly. It's also very simple manage all your data. It even has built-in discussion forums for support and feedback as well as issue tracking. This is perfect for API support when things go wrong. So, what the hell, I liked it so much signed up for the basic plan.

A very large chunk of the API documentation has already been completed and I'm hoping to get most of it done by this weekend. Hopefully, if all goes well, I can get a few people together to begin testing the API out.

Stoked!

As always, be sure to follow us on Twitter and check the site out!

Loading mentions Retweet