Browsing through the API docs at http://awestruct.org/yardoc/, I noticed that all the links to API members result in "Not Found" errors. Any chance to get this fixed?
I strongly recommend that we drop publishing the yardoc to the Awestruct site and just link out to the hosted API documentation on rubydoc.info. The benefit is that it makes the API doc available for all versions.
On Mon, Jun 8, 2015 at 8:26 AM, Gunnar Morling <[hidden email]> wrote:
Hi,
Browsing through the API docs at http://awestruct.org/yardoc/, I noticed that all the links to API members result in "Not Found" errors. Any chance to get this fixed?
I never understood why Bob went with the yardoc anyway.
On Mon, Jun 8, 2015 at 12:12 PM, Dan Allen <[hidden email]> wrote:
I strongly recommend that we drop publishing the yardoc to the Awestruct site and just link out to the hosted API documentation on rubydoc.info. The benefit is that it makes the API doc available for all versions.
On Mon, Jun 8, 2015 at 8:26 AM, Gunnar Morling <[hidden email]> wrote:
Hi,
Browsing through the API docs at http://awestruct.org/yardoc/, I noticed that all the links to API members result in "Not Found" errors. Any chance to get this fixed?
yardoc is fine, I just don't see why we need to publish it ourselves when there are multiple places where it gets published online. It's still yardoc, though, as far as I understand.
I think we should consider linking there instead. wdyt?
-Dan
On Tue, Jun 9, 2015 at 7:21 PM, Jason Porter <[hidden email]> wrote:
I never understood why Bob went with the yardoc anyway.
On Mon, Jun 8, 2015 at 12:12 PM, Dan Allen <[hidden email]> wrote:
I strongly recommend that we drop publishing the yardoc to the Awestruct site and just link out to the hosted API documentation on rubydoc.info. The benefit is that it makes the API doc available for all versions.
On Mon, Jun 8, 2015 at 8:26 AM, Gunnar Morling <[hidden email]> wrote:
Hi,
Browsing through the API docs at http://awestruct.org/yardoc/, I noticed that all the links to API members result in "Not Found" errors. Any chance to get this fixed?
Thanks for sharing these links, I was not aware of these sources.
Personally I find http://www.rubydoc.info/gems/awestruct/ a bit nicer, as it has the browsable view on the left side. In OmniRef it took me a bit to find out how to navigate through the pop-up menu.
yardoc is fine, I just don't see why we need to publish it ourselves when there are multiple places where it gets published online. It's still yardoc, though, as far as I understand.
I think we should consider linking there instead. wdyt?
-Dan
On Tue, Jun 9, 2015 at 7:21 PM, Jason Porter <[hidden email]> wrote:
I never understood why Bob went with the yardoc anyway.
On Mon, Jun 8, 2015 at 12:12 PM, Dan Allen <[hidden email]> wrote:
I strongly recommend that we drop publishing the yardoc to the Awestruct site and just link out to the hosted API documentation on rubydoc.info. The benefit is that it makes the API doc available for all versions.
On Mon, Jun 8, 2015 at 8:26 AM, Gunnar Morling <[hidden email]> wrote:
Hi,
Browsing through the API docs at http://awestruct.org/yardoc/, I noticed that all the links to API members result in "Not Found" errors. Any chance to get this fixed?
On Jun 9, 2015, at 9:21 PM, Jason Porter <[hidden email]> wrote:
I never understood why Bob went with the yardoc anyway.
On Mon, Jun 8, 2015 at 12:12 PM, Dan Allen <[hidden email]> wrote:
I strongly recommend that we drop publishing the yardoc to the Awestruct site and just link out to the hosted API documentation on rubydoc.info. The benefit is that it makes the API doc available for all versions.
On Mon, Jun 8, 2015 at 8:26 AM, Gunnar Morling <[hidden email]> wrote:
Hi,
Browsing through the API docs at http://awestruct.org/yardoc/, I noticed that all the links to API members result in "Not Found" errors. Any chance to get this fixed?
Locked
