mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
92 lines
4.0 KiB
TypeScript
92 lines
4.0 KiB
TypeScript
import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
|
|
|
|
import { StepDefinition } from '../steps'
|
|
|
|
export const getWebSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
|
|
const { CodeBlock, Markdown, Tab, dedent, snippets } = ctx
|
|
|
|
const JSEventCapture = snippets?.JSEventCapture
|
|
const JSHtmlSnippet = snippets?.JSHtmlSnippet
|
|
const JSInitSnippet = snippets?.JSInitSnippet
|
|
|
|
return [
|
|
{
|
|
title: 'Choose an installation method',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
You can either add the JavaScript snippet directly to your HTML or install the JavaScript SDK
|
|
via your package manager.
|
|
</Markdown>
|
|
|
|
<Tab.Group tabs={['HTML snippet', 'JavaScript SDK']}>
|
|
<Tab.List>
|
|
<Tab>HTML snippet</Tab>
|
|
<Tab>JavaScript SDK</Tab>
|
|
</Tab.List>
|
|
<Tab.Panels>
|
|
<Tab.Panel>
|
|
<Markdown>
|
|
Add this snippet to your website within the `<head>` tag. This can also be
|
|
used in services like Google Tag Manager:
|
|
</Markdown>
|
|
{JSHtmlSnippet && <JSHtmlSnippet />}
|
|
</Tab.Panel>
|
|
<Tab.Panel>
|
|
<Markdown>
|
|
{dedent`
|
|
Install the Insights JavaScript library using your package manager.
|
|
Then, import and initialize the Insights library with your project token and host:
|
|
`}
|
|
</Markdown>
|
|
<CodeBlock
|
|
blocks={[
|
|
{
|
|
language: 'bash',
|
|
file: 'npm',
|
|
code: dedent`
|
|
npm install insights-js
|
|
`,
|
|
},
|
|
{
|
|
language: 'bash',
|
|
file: 'yarn',
|
|
code: dedent`
|
|
yarn add insights-js
|
|
`,
|
|
},
|
|
{
|
|
language: 'bash',
|
|
file: 'pnpm',
|
|
code: dedent`
|
|
pnpm add insights-js
|
|
`,
|
|
},
|
|
]}
|
|
/>
|
|
{JSInitSnippet && <JSInitSnippet />}
|
|
</Tab.Panel>
|
|
</Tab.Panels>
|
|
</Tab.Group>
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
title: 'Send events',
|
|
badge: 'recommended',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
Once installed, Insights will automatically start capturing events. You can also manually send
|
|
events to test your integration:
|
|
</Markdown>
|
|
{JSEventCapture && <JSEventCapture />}
|
|
</>
|
|
),
|
|
},
|
|
]
|
|
}
|
|
|
|
export const WebInstallation = createInstallation(getWebSteps)
|