https://download.lucee.org/#37C61C0A-5D7E-4256-8572639BE0CF5838 The sum-total of the docs for this seems to be; "Extension for ESAPI functions". Are there any other docs? Which functions in CFML are "ESAPI functions" Do I need to go through docs.lucee.org for all matches of "*Requires Extension:* ESAPI extension"? I tried to find a section in there covering "ESAPI functions", but if it's there, it's eluding both me and Google. If indeed I am not missing something (entirely likely: this is the first time I've had to deal with a Lucee extension), could we get those docs augmented to list which functions it provides for? Even if the docs are maintained somewhere else (like at its source code repo on GitHub?) then just a link would suffice. I mean I could guess. But I really shouldn't have to, yeah?

18 items on both those pages. Which is slightly at odds with the 24 google claims are documented as being part of that extension. Obvs (?) the code is the source of truth though. I will try to find time to see what the other six are google mentions and see why they're not in the code (or if Google's doubling up or whatevs... I didn't check the values, just the count)

hmm, that might get complicated when you start considering that normal file/directory functions might rely on, say, the s3 extension, or some other extension based on the path. (maybe the docs already deal with this in some way, though--i haven't checked.)

Sure, 100%. I was not suggesting a template approach for "the way to document extensions". You do point out that the docs need to go both ways, eg: for

fileRead

the docs need to be clear and specific "if you wanna use this on s3, you need the extension [link to extension]", and for the docs for the extension, "adds s3 support to [list of CFML functions / tags here]". And if there's something else that needs documenting too... then document that too.