feat: support additional analytics providers beyond Google Analytics
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 12h 29m
- Merged PRs (30d)
- 12
Description
Problem
The analytics config schema only supports Google Analytics:
```yaml
analytics:
googleAnalytics:
measurementId: G-XXXXXXXXXX
```
Adding Plausible, PostHog, Segment, or other providers requires a schema rewrite and new provider code.
Suggested Approach
- Extend the analytics schema to support a provider pattern:
```yaml
analytics:
enabled: true
provider: plausible # or google, posthog, segment
config:
domain: docs.example.com
``` - Or support multiple concurrent providers (GA + Plausible)
- The existing `analytics` library already supports plugins — leverage that
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the analytics config schema and the existing analytics library's plugin support. Decide whether the provider pattern or concurrent-provider model is in scope, then trace the existing Google Analytics path. Done means the schema and provider integration support the agreed additional-provider behavior without breaking the current Google Analytics configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100