You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a number of improvements that could be done to the page-feedback feature. Given the issues that exist with analytics (blockers & consent), I'm not sure whether it's worth investing too much time here. Taking note nonetheless:
i18n support for the yes and no responses (I thought that I'd seen an issue go by that reported this but I can't find it)
Programmatic support for links into page URL, somewhat like the edit/view-page-source repo feature.
The text was updated successfully, but these errors were encountered:
Here's an example of page responses, making it obvious that we need i18n support. This is a screen shot after having clicked the positive response, from https://example.docsy.dev/fa/docs/:
Given the extent to which analytics events are being blocked by users nowadays, how much do we want to invest in improving the page feedback feature? Does it need to be reengineered to avoid relying on analytics events, and instead use something more GDPR friendly?
There are a number of improvements that could be done to the page-feedback feature. Given the issues that exist with analytics (blockers & consent), I'm not sure whether it's worth investing too much time here. Taking note nonetheless:
yes
andno
responses (I thought that I'd seen an issue go by that reported this but I can't find it)The text was updated successfully, but these errors were encountered: