Any Widget examples that use TypeScript and Nodejs?

Robert Nash Ben Tiedt  Grant Pankonien  any thought on how to approach TypeScripting projects with Community? 

I think I need a diagram to understand the architecture of what you are building?

Thanks for the response... I will put something together... a diagram would help me too.. 

The below are the systems that build, compile, convert, or deploy the code... 

I can send you the drawio file if you need it. I provided what's going on in the external development.. using the existing diagrams for telligent using REST API and the Webhooks.

again.. thanks for the response... 

So this is the drawing of how the application is interacting with Community.. the webhooks are something I have not used... Do I need to create the webhook then to allow working externally? or does it exist already?

a third diagram is needed that shows after the development is done... The Node JS listener is going to be a little difficult since, I've not thought that thru, but it seems feasible. I will update this post if I can form an image of what happens in the Widget API or somewhere else that replaces the webhooks, maybe sockets, which I've used.
Right.. we don't want to use WebHooks on premise?
Here are the steps based on the diagram above:

1. Create Node JS Web Application running locally
2. Build WebHooks in Visual Studio as a plugin, deploy to Community Web Server
3. Establish Node JS listener for webhook changes
4. Create Application using REST API for client application
5. When done, deploy the components, as a javascript api
6. Create the Telligent Custom Plugin as an Application, following the content model
7. Add Widgets as part of the Plugin
8. Use the Widget Studio, to modify Widget before "baking it" as part of the Plugin
9. Finalize it.

I should add in the unit test for each part to make sure they work, before going to the next steps, otherwise I'm going to need to repeat this process a lot.

Regarding webhooks, you could also implement custom outgoing hooks via Automation Studio--this would both allow you to leverage scripting for development and you could customize your hook messages for your application for efficiency.

The node app could then either use the REST API or communicate back to the automation (automations can send and receive HTTP requests and handle platform events).

Regarding webhooks, you could also implement custom outgoing hooks via Automation Studio--this would both allow you to leverage scripting for development and you could customize your hook messages for your application for efficiency.

The node app could then either use the REST API or communicate back to the automation (automations can send and receive HTTP requests and handle platform events).