I don't have any additional docs but here are some tips from my adventures setting up Facebook meta tags on the Herald and Miami.com pages.
Make sure to put the FB JavaScript SDK code in the body. It didn't seem to work when put in the head (probably because it uses a <div> tag). Alternatively, you could possibly split up the SDK call if you want the <script> tag in the head and the <div> in the body but we did not try this.
MI's hash tags: These seem to be counted by FB as separate URLs. This can result in the same story being listed in the recommended links multiple times. So there is some debate on their effectiveness. We are using the same hash tag (#storylink=fbuser) for multiple situations.
Additional tag attributes: I added some simple undocumented tag attributes so it seems like it's OK to experiment (I don't remember which, though but I think it was something like height having some effect).
Errors: I occasionally (rarely) see error messages when loading a widget. I'm not sure why this happens but the messages sometimes have to do w/ cross-site security errors.
On our Miami.com story pages, we have a narrow center rail FB widget that doesn't format properly in IE (site name wraps under logo instead of floating to the left). There's nothing we can really do about that because the content loads in an iframe, the same as if you added the widget's iframe manually.
Like Button popup comment box: When the user is logged into FB and clicks the Like button, they are presented a layer underneath the button that asks them to submit a comment. We had to modify the site design to make sure it was not getting accidentally hidden.
We had to get a Page ID to use the Like Box and also wanted several developers to have access. This requires an approval process and the developers need to accept the invite in a notification that we had trouble finding sometimes. I think it's a link on their notifications page at the bottom.