John Fairhurst

This is a Swift issue -- they give both methods the same 'unique' USR. It might be possible to work around in sourcekitten.

You'll need to customise the theme and make the changes there. Change `display: none` to `display: block` for `.height-container` in jazzy.css.scss, and, if your theme is using it, add the...

The top-level `yams.json` looks to have just the top-level contents, the directory structure below has the individual symbol data and hierarchy. Although this is derived from symbolgraph json (that jazzy...

This is a mixture of bugs and 'how things happen to work'. A SourceKit bug means that `typealias` declarations need a doc-comment for jazzy to even see them, and explicit...

Do you mean installing jazzy via homebrew or having jazzy document homebrew things in some way? If the first, previous discussion in #134. I'm not sure anything has changed since...

Closing this, clear that ruby gems don't belong in home-brew.

Yes I think this is doable -- I would go with syntax like `- docs-category: MyCategory` to fit in with the callout convention, this will also hide it in Quick...

Can you say a bit more about your use cases here? Are you imagining using this in doc comments or the separate markdown documents? Would you want jazzy to include...

Jazzy doesn't have great support for including resources like images in the site, you have to do it manually as you've found. #853 is about fixing this, I added some...

Right, currently you have to use the `@param` syntax in Obj-C mode. Not done much testing on non-HeaderDoc -- latest Xcode 'generate-doc-comment' still generates HeaderDoc syntax.