Waylan Limberg

I think leaving templates as something to tackle later is a reasonable approach. My initial proposal was simply trying to present an ideal situation from the user's perspective with no...

> I think I'm ready to discuss the syntax. I like the general idea here. Overall, it seems like a great start. I will address each item in turn below....

Ah, I had missed that this is copying a pre-existing implementation (Myst). Now it makes more sense to me. The one concern I have is that Myst is specifically intended...

I am not opposed to having an API document. It would likely be helpful to extension developers. However, it should not replace the existing user documentation. I am a firm...

> I could then start with a basic, recursive generation of the docs for each module (just as shown in the screenshot above), and you can tell me which member...

> I've implemented a way to merge `__init__` methods docstrings and signatures into their class'. 👍 I like it. > Maybe less disruptive - list style: Yeah, I agree. Let's...

> I also agree that auto-linking to builtin types is not really useful. However there's no way yet to ignore parts of a loaded inventory. Ah, okay. I guess I...

> """ > extensions (list[str | Extension]): ... > """ Cool. I wasn't aware of that. I find this syntax more readable. Let's go with it if we can. >...

> I suppose one approach would be to use the short version in the annotation (Extension), To be clear, I am speaking about what gets rendered. I understand that the...

Just a reminder to myself: Lots of test cases in [these](https://github.com/michelf/php-markdown/issues/9) [bug](https://github.com/michelf/php-markdown/issues/10) [reports](https://github.com/michelf/php-markdown/issues/11).