Consider pruning links to projects that are no longer actively supported or off brand

[jpjpjp]

This wonderful resource has been around for some time. Since its original creation the branding of the product has changed (from Spark to Webex Teams) and many of the authors of the original projects are no longer actively maintaining them.

As a curated list, I think it is healthy to occasionally "prune" it, by removing references to older projects that are not supported or refer to older processes, especially in cases where an updated replacement may be available.

As an example, the awesome node-flint framework created by @nmarus, is unfortunately no longer being actively maintained by him, however a new framework the webex-node-bot-framework, inspired by flint is available. Rather than having this curated list include both frameworks, perhaps it makes more sense to keep only the latest supported version.

Similarly, the sparkbot-starter project created by @valgaze, is great but is no longer on brand and is based on the older flint framework. Luckily there is a new webex-bot-starter that is based on Victor's work but using the newer framework and new branding name. Does it make sense to keep both of these projects on this list?

Of course it always makes sense to check with the authors of projects that are candidates for pruning. If they wish to update their projects to keep them here, that is the best case scenario!

[valgaze]

@jpjpjp Very much agree on all counts-- prune it!

I think this is the best bet: https://developer.webex.com/blog/from-zero-to-webex-teams-chatbot-in-15-minutes

I've been doing a lot of work on collab libraries & lately integrating w/ ai services & I'll definitely have some other guides in the future

The "From Zero to XXX" titling has been really successful & easy to grasp-- maybe there ought to be an effort for subject matter experts to create canonical "From Zero to XXX" on any services that would lend themselves to that kind of structure

It's like the old "features tell, benefits sell" cliche-- make available content that right away demonstrates useful/valuable functionality and then fill in the details w/ best practices