implement pushfeedback

[christinaausley]

Description

Option #2 for the PushFeedback widget -- relates to #355.

This option uses Swizzling to extend our footer, essentially:

And when a user clicks either the thumbs up or thumbs down they see:

This takes care of the location issues I was having in #3812, but I can't figure out how to customize the pop-up modal to adjust its coloring and such. Thoughts @pepopowitz?

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @christinaausley as a reviewer.

[akeller]

Since we have the Ask AI button, this is my preferred integration. Let's chat more on our internal devex channel about next steps @christinaausley.

[akeller]

🟢 This gets my stamp of approval (and, for internal purposes, your line manager's stamp of approval).

@christinaausley will work through the vendor/new tool process internally. Thanks for getting this rolling!

[christinaausley]

This is ready for final review @pepopowitz @akeller 👍

[akeller]

Adding deploy tag to help with review.

[github-actions]

🧹 Preview environment for this PR has been torn down.

[pepopowitz]

This is awesome!!!! Great work!!

The only blocking request I have is that we add some information about why we are swizzling this component. I also added some comments related to a non-blocking styling nit.

I will also mention that I was unable to submit feedback through the preview site, with a message from PushFeedback that it was coming from a URL that they didn't recognize. I assume this will all just work when we go live, submitting feedback from the docs.camunda.io URL.

[christinaausley]

Thank you @pepopowitz! 🥳

[akeller]

No blocking concerns from me.

If possible, we may want to add stage.docs.camunda.io to the list of URLs PushFeedback allows so we can test this before it goes all the way live, but I'm also fine with testing in production and removing it if we see anything concerning. YOLO

[pepopowitz]

❤️ ❤️ ❤️

[christinaausley]

We can only set one domain per "project" with PushFeedback, so I'm going to ship this. If anything wonky pops up I'll backtrack and create a new project with the staging domain to test more thoroughly.