Conversation
…alytics and experiments integration ## Summary Introduces a new example project demonstrating the integration of dotCMS Content Analytics and A/B Experiments using Next.js. This example features a minimal headless setup with separated integration for analytics and experiments. ## Changes - Created a new directory `examples/nextjs-analytics-experiments` containing: - Configuration files (`package.json`, `tsconfig.json`, etc.) - Environment variable example (`.env.local.example`) - Core components and pages for handling analytics and experiments - Utility functions for fetching dotCMS pages and handling responses - Basic styling with Tailwind CSS ## Verification Run the example with `npm install` and `npm run dev` to start the local server. Closes #36200 🤖 Generated with [Claude Code](https://claude.com/claude-code)
…ing integration ## Summary Enhances documentation for the `@dotcms/experiments` SDK and related examples, providing clearer guidance on A/B testing integration with Next.js. ## Changes - Added sections on Public API, Troubleshooting, and Anti-patterns in `core-web/libs/sdk/experiments/README.md`. - Updated example files to clarify the separation of analytics and experiments, emphasizing the importance of unconditionally calling `withExperiments`. - Improved descriptions in `examples/nextjs/README.md` and `examples/nextjs-analytics-experiments/README.md` to guide users on best practices for using the SDK. ## Verification Review the updated documentation and examples to ensure clarity and correctness. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
❌ Issue Linking RequiredThis PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes. How to fix this:Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Why is this required?Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.--- This comment was automatically generated by the issue linking workflow |
github-actions
Bot
added
Area : Frontend
🤖 Bedrock Review —
|
|
Claude finished @nicobytes's task in 1m 16s —— View job Rollback Safety Analysis
Result: ✅ Safe To RollbackAll changes in this PR are documentation, examples, and DevOps tooling — none fall into any rollback-unsafe category. Changes reviewed:
No database migrations, no Elasticsearch mapping changes, no REST/GraphQL API contract changes, no content model changes, no OSGi interface changes, and no VTL viewtool contract changes are present. Label |
| "nx-mcp@latest" | ||
| ] | ||
| }, | ||
| "primeng": { |
There was a problem hiding this comment.
because is dead, not working, I guess.
|
@copilot resolve the merge conflicts in this pull request |
# Conflicts: # core-web/libs/sdk/experiments/README.md
Resolved. I merged |
This pull request introduces significant improvements to the documentation, configuration, and usage guidance for the
@dotcms/experimentsSDK, especially in the context of Next.js integration. It also includes updates to example environment files, gitignore, and Docker compose scripts for better developer experience and reliability.Documentation and Usage Improvements:
Major rewrite and expansion of the
core-web/libs/sdk/experiments/README.md:withExperimentsis public and that internal providers should not be imported directly. [1] [2]Updates JSDoc for
DotExperimentsProviderto mark it as internal and discourage direct usage, reinforcing the intended public API.Next.js Example Project Enhancements:
.env.local.examplefor the Next.js analytics/experiments example, detailing all required environment variables and their purpose..gitignoretailored for Next.js projects, covering dependencies, build artifacts, environment files, and debugging logs.AGENTS.mdandCLAUDE.mdwith agent-specific instructions and references for the example project. [1] [2]DevOps and Tooling Reliability:
docker compose(v2 plugin) and legacydocker-compose, and uses the correct command for listing running services. [1] [2]Build and Configuration Cleanup:
primengentry from.cursor/mcp.jsonand formats theangular-clicommand arguments for clarity.These changes collectively make the SDK easier to use correctly, improve developer onboarding, and reduce the risk of common integration pitfalls.