Eugen

Thanks, @cognifloyd for trying it! Really helpful to have an example :+1: The diff key points to me: 1) URLs https://st2docs.readthedocs.io/en/rtd/actions.html vs https://docs.stackstorm.com/actions.html Migration-wise, all the links because of SEO,...

@cognifloyd Speaking of Preview & Security, why not have both? We could just keep RDT integration for PR preview only on that development URL, while actually deploying the "production" https://docs.stackstorm.com/...

The updated theme looks ok, just still need to preserve the original page width as before: **OLD**  **NEW** 

@HankTheCrank As @punkrokk noted, please report the exact error message you're seeing. ---- Some of the packs rely on libraries that are not shipped with the default OS distribution. For...

+1 good stuff. @mickmcgrath13 want to create a better documentation around that, maybe together with @punkrokk? Keeping in mind his past experience in building his own index fork, that might...

Did you take a look for any errors in the web browser developer console?

Thanks for submitting the bug report, @sk8erwitskil!

This sounds like a bug indeed as secrets should be masked. Thanks for the report. If someone is interested in contributing, the fix should be done in the st2 core...

Oh, I could find related discussion: https://github.com/StackStorm/st2web/pull/191 Is something like that already implemented?

Yeah, as I checked, data about the nested properties is returned from API. So it's only about `st2web` implementation. Majority of data returned from Sensors is structurized and nested this...