-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to write documentation? #162
Comments
Have a look at http://nshipster.com/swift-documentation/, it has a nice overview. Otherwise, please be more specific about how what jazzy renders differs from what you were expecting. |
Thanks @segiddins. I did look at mattt's article. Let's be specific with, paragraphs, for example. Here is a simple example where jazzy does not render correctly paragraphs: /**
The template's base context: all rendering start from this context.
Its default value comes from the configuration of the template
repository this template comes from.
:see: repository
*/
public var baseContext: Context Xcode shows two paragraphs: Jazzy shows a single one: |
Is there a reason that things like :see show up as small text rather than a section like the Apple documentation. Also it would be great to add a quick example usage and maybe a list of supported markup. The NSHipster article only references :params and :returns. Not sure if any sort of code blocks, See Also, Note, or Discussion are supported. Not sure if I am doing something wrong or it just isn't supported yet. |
That's a rendering issue with jazzy's CSS which we haven't gotten to fixing, though you're welcome to do so yourself. Help is always appreciated 😄. |
Sounds good. If I get some time I'll play around with it. Thanks |
Closing as a duplicate of #77. |
Which format should we use to document our types and methods?
How can we render:
Maybe the jazzy README could sport sample Swift and Objective-C code, and a link to the generated documentation. That would be a nice introduction.
Today, I have difficulties having jazzy rendering a honest Swift documentation like the one below.
The text was updated successfully, but these errors were encountered: