Improving the Install page #7443
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
joethreepwood
commented
Jan 4, 2024
joethreepwood
commented
Jan 4, 2024
joethreepwood
commented
Jan 4, 2024
Closed
28 tasks
ivanagas
approved these changes
Jan 4, 2024
|
|
||
| Paste this snippet within the `<head>` tags of your website - ideally just inside the closing `</head>` tag - on all pages that you wish to track. | ||
| Copy the snippet below and replace `<ph_project_api_key>` and `<ph_instance_address>` with your project's values, then add it within the `<head>` tags of your product - ideally just before the closing `</head>` tag - on pages you want to track. |
There was a problem hiding this comment.
One thing is the <ph_project_api_key> and instance_address get automatically filled if those details are available (I think by using the logged in cookie), so there is a chance someone sees this and they don't have those values below.
There was a problem hiding this comment.
Hm. Not sure I can see how we can accomodate that though. Probably best to leave it?
ivanagas
reviewed
Jan 4, 2024
xrdt
reviewed
Jan 4, 2024
xrdt
reviewed
Jan 4, 2024
Co-authored-by: Bianca Yang <[email protected]>
Co-authored-by: Ian Vanagas <[email protected]>
Co-authored-by: Ian Vanagas <[email protected]>
joethreepwood
commented
Jan 5, 2024
Co-authored-by: Ian Vanagas <[email protected]>
Co-authored-by: Ian Vanagas <[email protected]>
joethreepwood
commented
Jan 5, 2024
Co-authored-by: Ian Vanagas <[email protected]>
Co-authored-by: Ian Vanagas <[email protected]>
joethreepwood
commented
Jan 5, 2024
|
|
||
| > **Tip**: Even if you have multiple customer-facing products e.g. a marketing website + iOS app + web app, it works best to have them share the same project to track the user across their journey. See: [Organizations & projects docs](/manual/organizations-and-projects) | ||
| > **Tip**: If you have multiple customer-facing products (e.g. a marketing website + iOS app + web app), it's best to install PostHog on them all and [group them in one project](/docs/data/organizations-and-projects). This way you can track the user across their entire journey. |
There was a problem hiding this comment.
Suggested change
| > **Tip**: If you have multiple customer-facing products (e.g. a marketing website + iOS app + web app), it's best to install PostHog on them all and [group them in one project](/docs/data/organizations-and-projects). This way you can track the user across their entire journey. | |
| > **Tip**: If you have multiple products (e.g. a marketing website + iOS app + web app), it's best to install PostHog on them all and [group them in one project](/docs/data/organizations-and-projects). This way you can track the user across their entire journey. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
One of my Q1 goals is improving the getting started content, so it makes sense to start here.
The existing version (above) is...
>sections + a code snippet)It also doesn't mention that we recommend setting up a reverse proxy, even though we recommend doing this and it will soon feature as a step in @corywatilo's new onboarding flows.
Addressing these points gives us a much tidier, simpler install page while still giving us room to include the reverse proxy.
Checklist
vercel.jsonArticle checklist
Useful resources