<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Luz,</div><div class=""><br class=""></div><div class="">We currently have no standard established for generating documentation for packages in a uniform way, but it's in our plans (<a href="https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageManagerCommunityProposal.md#documentation-generation" class="">https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageManagerCommunityProposal.md#documentation-generation</a>). Proposals are welcome for how to do this, via the swift evolution process (<a href="https://github.com/apple/swift-evolution/blob/master/process.md" class="">https://github.com/apple/swift-evolution/blob/master/process.md</a>)</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre">        </span>- Rick</div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 13, 2015, at 6:11 PM, Luz Violeta via swift-users &lt;<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hello everyone ! o/</div><div class=""><br class=""></div><div class="">I've been poking around with swift on Linux and suddenly I got interested in how to write docs and generate appropriate html/pdf/whatever files for consumers of a package.</div><div class=""><br class=""></div><div class="">I found in .build that a binary file *.swiftdoc is generated but I had no idea if there's a tool available, specs or something to make it usable ...</div><div class=""><br class=""></div><div class="">Any pointers? Ty for reading&nbsp;</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=qz0eNO-2BnIaKwfHdqdSEoWDzK1gYoMlfMcRDuURe6g4ktcAsnll1Ei-2BaZY0KI3nX5k6W6vRR6cLHmGgrsRwOyyrFPq7sOAsWibdWeOak3u4XCIbuRwAG4Bw8qkFqh655-2FoB-2FlwK9W2UOPU1ZpCIN3-2B5f6or97nXyc6TFo1EYgJc3rQZk0tIZI5mACVyYB-2Fb7SjiAKjTGce1ZhFuB4UTqNkH-2B56y0j2HjVFPSe-2B7RnMw8-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-users mailing list<br class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-users<br class=""></div></blockquote></div><br class=""></body></html>