Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Ability to link to feature #9509

Closed
joethreepwood opened this issue Apr 25, 2022 · 4 comments
Closed

Feature Request: Ability to link to feature #9509

joethreepwood opened this issue Apr 25, 2022 · 4 comments
Labels
enhancement New feature or request stale

Comments

@joethreepwood
Copy link
Contributor

Is your feature request related to a problem?

There's some context on this .com PR: PostHog/posthog.com#3350

But the short version is that it would be a useful improvement to the docs, content, site CTAs, etc. if we could link users to specific features or areas of the product. Currently, from discussion in Iceland with @pauldambra I believe we can do this for Cloud users, but because self-hosted users have more unpredictable domain names.

This would be helpful for CTAs in the docs, links in product announcements and Array posts, as well as for use by Support Hero.

Describe the solution you'd like

"Interested in Funnels? [Give it a go!](link to funnels in app]"
"Want to try this plugin? [Install it now.](link to specific plugin)"

Existing, logged in users would click the linsk above and be taken to the relevant feature on their instance (and probably their most recent project, if multiple). Users who do not have an account or who are not logged in would be directed to /signup to start creating an account.

Describe alternatives you've considered

As per the PR above, we've discussed other ways of working useful CTAs into Docs, but concluded this may be the best.

Additional context

Thank you for your feature request – we love each and every one!

No, thank you, team!

@joethreepwood joethreepwood added the enhancement New feature or request label Apr 25, 2022
@pauldambra
Copy link
Member

In the discussion in Iceland I suggested you could let someone set what their PostHog URL was through to (an admittedly very complex implementation of) doing the oAuth dance to log into posthog.com with their PostHog account so we can detect the URL to use

@joethreepwood
Copy link
Contributor Author

In the discussion in Iceland I suggested you could let someone set what their PostHog URL was through to (an admittedly very complex implementation of) doing the oAuth dance to log into posthog.com with their PostHog account so we can detect the URL to use

You did, but IIRC we ended on that not being a great solution because it wouldn't work well if someone wasn't logged? Though I may have misunderstood (and wouldn't know how to ship that myself anyway).

@pauldambra
Copy link
Member

Yep, I think it's a tricky thing however you cut it...

But letting someone set a desired PostHog URL and rendering links differently if they have is relatively straight-forward.

TBH The tricky bit would be detecting drift if PostHog URLs changed... e.g. when we changed insight URLs to use short ids instead of long filter params

@posthog-bot
Copy link
Contributor

This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

3 participants