Add Reo.dev analytics tracking

[azaddhirajkumar]

Integrates Reo.dev tracking beacon to monitor developer activity on the documentation site. Adds the Reo.dev JavaScript snippet and configures Docusaurus to load it on all pages.

https://docs.reo.dev/integrations/developer-docs/docusaurus

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces Reo.dev analytics tracking to the documentation site. The primary goal is to gain insights into developer activity and engagement with the documentation, which will help in understanding user behavior and optimizing content. This integration involves adding a custom JavaScript beacon and updating the site's configuration to ensure the tracker loads correctly across all pages.

Highlights

• Reo.dev Analytics Integration: Integrated Reo.dev tracking beacon to monitor developer activity on the documentation site.
• Docusaurus Configuration Update: Configured Docusaurus to load the Reo.dev JavaScript snippet on all pages by adding a new script entry to docusaurus.config.js.
• Custom Tracking Script: Added a new JavaScript file, custom-reo.js, containing the Reo.dev initialization code.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• docusaurus.config.js
  • Added a new scripts array to the configuration to include custom-reo.js.
• static/scripts/custom-reo.js
  • Created a new file to house the Reo.dev tracking snippet, including its initialization with a client ID.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds Reo.dev analytics tracking. The implementation introduces a hardcoded client ID and a minified script into the codebase. My feedback focuses on improving maintainability and security by suggesting the use of environment variables for the client ID and storing readable, un-minified code in the repository.

[gemini-code-assist]

This file contains a hardcoded client ID and is minified, which presents maintainability and potential security issues.

1. Hardcoded ID: Hardcoding configuration values like this client ID makes it difficult to manage different environments (e.g., development vs. production) and to rotate keys if needed. It's a best practice to load such values from environment variables.
2. Minified Code: Including minified code in source control harms readability and maintainability. It's better to commit the original, formatted source code.

To address this, I recommend converting this to an inline script within docusaurus.config.js. There, you can use process.env to securely load the client ID from an environment variable and avoid committing minified code.

Suggested change

	!function(){var e,t,n;e="3b8cf05627127ba",t=function(){Reo.init({clientID:"3b8cf05627127ba"})},(n=document.createElement("script")).src="https://static.reo.dev/"+e+"/reo.js",n.async=!0,n.onload=t,document.head.appendChild(n)}();
	(function() {
	// TODO: This client ID should be loaded from an environment variable, not hardcoded.
	const clientId = "3b8cf05627127ba";
	function initReo() {
	if (window.Reo) {
	window.Reo.init({ clientID: clientId });
	}
	}
	const script = document.createElement("script");
	script.src = `https://static.reo.dev/${clientId}/reo.js`;
	script.async = true;
	script.onload = initReo;
	document.head.appendChild(script);
	})();

[jayant-dhingra-cb]

Looks good