I'm going to say what I have to say then drop the subject. I have my own resource collection, and I can harvest resources mentioned in posts.
Your comment directly contradicts the consensus arrived at in [A Thought about the Sites Growing Discussions of Scripting]{A thought about the site's growing discussions of scripting}, where it seemed that everyone — @peterlewis in particular — agreed that anything to do with scripting was fair game for the site.
I don't at all see how [quote="JMichaelTX, post:7, topic:4126"]
We ALREADY have a place for resource links.
[/quote] I don't know where that is, how to find what's there, or add to it.
The purpose of what I wanted to propose was to extract and organize information that is already in posts, or will be in posts in the future, that
- aren't really directly relevant to the OP
- are scattered all over and difficult to find
- would not be something someone would search for if they did
The current Wiki is heavy-handed in that it requires write permission, is tightly constrained, and is being written by a very few people (2?). The original Wiki concept was that all pages were open for everyone to contribute. That is the best way to build a repository of communal resources.
the only top-level table of contents for the Wiki is one that reproduces the KM manual. It never occurred to me until engaging in this discussion that there were pages on other things in the Wiki, such as JavaScript for Automation. I tried something else: there's nothing on GUI Scripting. So it's really hit-or-miss and all based on search guesses.
Besides, sometimes someone wants to come at things not from a known topic but to find out what there is to know: all editors that could be used for scripting in one way or another, or IDEs. It would be good to have all that collected, rather than requiring queries, and it would be good for their to be an obvious pointer to the topic so that people who don't know it's there will see it.
I found one page with a few references to books on it. One page with four books? Consider how many books have been recommended in various posts.
I may be wrong but I don't think there is anything substantial about Swift in the Wiki, and Swift will become increasingly important.
Does anyone know what Xcode can do with AppleScript, if anything, and how?
What about the convenience of assembling reference material in one place. Is it worth saving people the trouble stumbling around looking for Apple's AppleScript Guide? Explaining that the only documentation on JXA is something called "Release Notes" (which sounds like an update, not the documentation itself)? Pointing to Apple videos not everyone know about or how to find? Would it be worth having a list of the top sites everyone goes to, such as MacScripter, for people who are using KM and just getting in to using it for AppleScript?
Would it good to have references to Markdown documentation, tutorials, and examples? It sure would have saved me some trouble and other people time answering my questions. I didn't even know that Discourse accepted full Markdown until recently. (Does everyone know how to tell Discourse what language to use in adding syntax highlighting for a code block?)
What about useful tools such as UI Browser and ScriptLight? What's the best editor for Markdown? For XML? How do you use the Safari debugger for JXA?
Even something as trivial as "which tool do you use for screen capture and markup" would be better collected on a page then sprayed all over posts to which they are not relevant. (I'm not saying that it's not OK to ask these questions in the middle of other posts, what I'm saying is that those posts do not serve as appropriate repositories for knowledge about the topic.)
I have lots more I could say, but I think I've said enough.