Repository navigation
Add Posthog analytics - #115
ElijahAhianyo wants to merge 7 commits into
Conversation
|
|
||
| static CONFIG: OnceLock<Result<AnalyticsConfig, String>> = OnceLock::new(); | ||
| const DEFAULT_ENABLED: bool = true; | ||
| const DEFAULT_PROJECT_TOKEN: &str = "phc_CpMFffYnhPmXZrMy8oh8TqeB2kK4EopYaMft3yhgtHiY"; |
There was a problem hiding this comment.
I think most of the code is logic for the cookie banner. Using PostHog with cookies requires a mandatory cookie banner for compliance reasons . Technically, we could use the cookieless option(Discussed this with @m4tx last week), but we lose some good analytics features that could give us more insight into improving the doc experience. |
I think I'd rather go with cookieless as a first step and see what value we can get from that and expand from that in the future. We all hate those cookie banners, so I'd try to not have to show them on our site (especially since it's static docs site), unless we actually need it. If you really want to go with cookie option, I'd redo the cookie banner to reduce the generic dry language with something more direct and "human". Like change the text to "Optional cookies help us figure out what’s working (and what’s not) so we can make the site better for you and everyone else." or "We’d like to use a few optional cookies to peek at how you use the site. No creepy stuff, just helping us make it better for everyone.". We could also extract the cat from our logo and put there in the corner to make it more individualized. |
@seqre to be fair, I actually just lifted this off the Mintlify docs: https://www.mintlify.com/docs and the GitBook docs: https://gitbook.com/docs/, but yeah I could improve that. My only issue is that this part, "No creepy stuff, just helping us make it better for everyone," makes it sound even more suspicious; maybe it's just me 😄
Where exactly should this go? The banner or the modal? Also, I'm wondering if we really need to have the logo there as well |


No description provided.