Request plugins explained

[v4hn]

The maintainers should read through the explanations and refine or correct them as required, before this goes to the website.
Here's the direct link: https://github.com/ros-planning/moveit.ros.org/blob/request-plugins-explained/documentation/plugins/index.markdown

@mikeferguson could you please have a look at the plugins you are/were involved in?
moveit/moveit#116 suggests that you are the best reviewer for the CollisionPlugin, but probably others too.

[davetcoleman]

I just documented PlanningRequestAdapter

[mintar]

As I mentioned in #55, this PR should be rebased onto gh-pages. The travis build will fail, which is a good thing: html-proofer caught its first real error (see the line comment I'll add in a few secs)!

[mintar]

This should be /documentation/plugins/, not /plugins/.

[mintar]

And perhaps move it up a bit. I think "FAQs" and "Code API" should be the last on that list, but that's a personal preference.

Also, the link to the plugin documentation should be added to documentation/index.markdown (to keep it consistent with the nav bar).

[v4hn]

feel free to file a request :)

[v4hn]

I corrected the broken link.

[mintar]

Thanks for rebasing! Could you also have a look at my second comment?

And perhaps move it up a bit. I think "FAQs" and "Code API" should be the last on that list, but that's a personal preference.

Also, the link to the plugin documentation should be added to documentation/index.markdown (to keep it consistent with the nav bar).

[mintar]

Ok, I've submitted a PR for that: #60 .

[davetcoleman]

I've just removed the "Documentation" page since it didn't have any real purpose (just an index) and it keeps the menu bar concise.

Nevermind... on further thought, I realize this is a bad idea because it serves as a landing page for documentation e.g. from the README.md for the moveit repo.

[davetcoleman]

Since WMD is over, I think we should go ahead and merge this with its remaining TODOs in place, and hopefully someone can fill it in as they feel compelled. By having the template ready and easy to find, someone is more likely to add to it in the future.

[v4hn]

Yeah, I'd like to merge this soon too.

Two things:

• @davetcoleman could you finish the description of PlanningRequestAdapter?
  The "Interface Description" part should additionally point to the header file that specifies the C++ interface one has to implement for a new plugin of that type and "Concrete Implementation" should link to the code of one implemented plugin.
• It would be great to have the different plugins a bit more visually separated from each other.
  Could we add (possibly thick) horizontal lines above each plugin header?

[davetcoleman]

I've added more info to PlanningRequestAdapter, added an extra thick line, and made each title easier to read. I also improved the way section links are used and reordered table of contents to match document.

This is ready to merge

[v4hn]

Merging.

Thanks to everyone who contributed!