richmond62 wrote: ↑
Wed Dec 18, 2019 9:36 am
what to do with the rest of "Talking LiveCode"
If you mean the 'Talking LiveCode' section of the Forums, you should just leave it as it is.
Please do not start purging messages that are relevant only to earlier recensions of LiveCode.
I wouldn't purge those. I rarely delete things that aren't obvious bot spam.
That one thread was an easy exception as it had only a handful of posts and no information of substance (people asking why there's a section on Solaris so long after Solaris reached EOL, and why Unix was mentioned at all in a topic ostensibly for an entirely different purpose).
With other threads no longer of value for members seeking support, if I do anything with them at all I would consider creating an archive section as many other forums have, and just move the threads without deleting them.
Or I may just leave those less relevant threads in place; it's a lot of work and moderating here is a volunteer activity. While I do try to be responsive to community input on things like this, the number of messages I get complaining about the ratio of signal-to-noise here is not yet high.
so many other corners of this long-in-the-tooth taxonomy
'taxonomy' is not the word I would have chosen here.
"Taxonomy" refers to the hierarchical ordering of a collection. In the literature on information systems design you'll find it used quite commonly.
But 'long-in-the-tooth' is true with regard to so much on the LiveCode website and parts
of the documentation. In fact some of it is so outdated it is positively misleading.
The LC web site and docs are separate concerns from this user-to-user support forum, with different means and personnel employed in their maintenance.
I have no mandate to clean up any other information systems for LiveCode beyond these forums, so for those I would ask once again that you please submit a bug report for any specific obvious errors or omissions you find in the docs or the web site. The bug DB includes flags for those types of requests.
If you see something specific but it's not obvious whether it's an error or omission, using the "Bug Reports" section of these forums to solicit input from other community members to refine the suggestion before submission works as well for content issues as it does for technical ones.
I don't know how Heather would react if someone downloaded web pages that contained outdated stuff,
edited them and then sent the edited versions to her for checking and re-upload.
If the writing is good, fits the tone of the site, and addresses an obvious issue, they may be delighted to have that included in a bug report. I've done that with Dictionary entries and a few site details, and they've always been welcomed.
Since the site is made with a CMS, editing the output HTML may not be the most efficient way to resolve an issue. Submitting the text by itself without the CMS' generated styling markup should be sufficient. If the content requires styled text, minimal inline tags may be helpful.