Clojurians Log v2

build failure for sci: https://cljdoc.org/builds/23234

maybe because I have some html files in my doc folder?

I generated those using codox

that multimethod should probably have a default value instead of failing

@borkdude html is not a supported file format in doctrees https://github.com/borkdude/sci/blob/master/doc/cljdoc.edn

I just want to make a link in the side menu 😕

I'll remove it then

@martinklepsch I don't understand why the page says missing scm info. I think I filled it in in project.clj

link: https://cljdoc.org/d/borkdude/sci/0.0.12-alpha.2

> I just want to make a link in the side menu What's in that HTML file that you can't put into a Markdown file?

codox-generated files

why? so http://borkdude.github.io/sci also works

HTML doesn't allow cljdoc to provide a uniform documentation viewing experience. That has downsides and upsides but cljdoc has always taken a stance on the side of consumers in terms of providing a streamlined reading/viewing experience

makes sense, I've already accepted that. moving on. I still don't understand why the page says missing scm info 🙂

Not sure I understand how cljdoc configuration is related to making the http://github.io page work

well, my assumption was that making a link in the cljdoc menu would just point to the static file and be done with it

I think that might solely due to the fact that the build failed, here's a build that worked and SCM info is shown properly: https://cljdoc.org/d/borkdude/sci/0.0.11-alpha.14/doc/readme

I'm sorry to dissappoint your assumption here 🙃

alrighty, I've re-triggered the build now

no biggie, have a nice day 🙂

you too 🙂

Oh and generally I'd be curious why the http://github.io page is important to you, as in what does it get you that cljdoc doesn't already provide?

javadocs

https://borkdude.github.io/sci/doc/javadoc/

Ah I see, well that makes sense then 🙂 I guess my recommendation would be adding a page to the doc tree "Java API" that then links to that page

ehm, that's exactly the thing you just said that didn't work?

I mean doc/java-api.md with some basic information on the Java API and a link to the generated javadocs. This way you keep all info in one place, the java API docs are easy to find and you can still use cljdoc as primary documentation hub with it's API docs for Clojure (in contrast to the github pages where you would have to manually publish Clojure API docs)

I already have a description of those java docs directly in the README.md

making an indirection .md file feels like a workaround (but definitely a possible workaround)

Yeah I mean you can also obviously just link to the Java docs from that section (as you already do) but IME adding more stuff to the sidebar helps discoverability of docs a lot

but yeah "depends" 🙂