kernc

Indeed. Sorry. It actually completely escaped my mind to look at the files. I only visually inspected the site. But I must confess to the latter, what does the PHP...

We, in fact, have [_pdoc/\_\_main\_\_.py_](https://github.com/pdoc3/pdoc/blob/master/pdoc/__main__.py), added in https://github.com/pdoc3/pdoc/pull/8 for precisely the reason of making the module executable. Can you say whether it's a case of https://github.com/pdoc3/pdoc/issues/131?

I don't mind using above snippet (the one without vendor prefixes). Some blank lines ([BMO#1273836](https://bugzilla.mozilla.org/show_bug.cgi?id=1273836)) are still better than nothing. PR welcome.

Is there an issue with making `.hljs-meta` tags not user-selectable as you proposed? I think it a legitimate request, and it should find its way into the codebase eventually. :smile:

> Docs hierarchy follows module hierarchy This is one of the selling points, so a strict, fully-functional module refname overriding is out of the question. You _could_ [override _html.mako_ template](https://pdoc3.github.io/pdoc/doc/pdoc/#custom-templates)...

I think it's safe to just generate the index.html always, why not? Didn't think of that in https://github.com/pdoc3/pdoc/issues/55. :+1: Besides the index file, why not list all top-level, disjunct packages/modules...

I'm hesitant adding command line flags for little used features. What do you need the index for and how often? Couldn't a simple shell script, iterating over the same packages...

I think, rather in factly, that a proper index is indeed in order, *spanning hierarchically all the way to leaf modules*. Created always. What users specify as `--output-dir` is pdoc's...

Exactly! Maybe without leading dots and more uniformly indented. Maybe with children also not necessarily exactly in the right grid column but somewhere in the middle.

> I'm having trouble picturing how this would look while keeping the uniform indentation. No, no, I meant uniform per nesting level, as in your last image already. :+1: Just...