Analytics and feedback

Use Plausible for basic documentation analytics. Add one Plausible site for each canonical documentation domain.

Commit the real script ID

Use the @nuxt/scripts Plausible registry integration that Ginko Docs exposes. Store the real Plausible script ID in the documentation app configuration. The ID is public configuration and is not a secret environment variable.

Do not copy a raw script element into Markdown or inject the same script by two paths. The rendered page must contain exactly one correct Plausible script.

This handbook intentionally omits analytics until oss.lupinum.com has a real Plausible site and script ID. Add it during the external launch setup. Do not invent a placeholder ID.

Collect useful feedback

Enable the Ginko Docs “Was this page helpful?” component. A response records a docs-feedback event when Plausible is active. The issue link opens a prefilled documentation report in the repository.

Confirm the event in Plausible after production deployment. A visible button does not prove event delivery.

Respect privacy

Do not add fingerprinting, session replay, or user identifiers for basic docs analytics. Link the production privacy policy from every page footer.