docs(budcustomer): add Customer Dashboard portal guide#1181
docs(budcustomer): add Customer Dashboard portal guide#1181
Conversation
Summary of ChangesHello @jithinAB, I'm Gemini Code Assist1! 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 significantly enhances the customer-facing documentation by introducing a dedicated guide for the Bud Customer Dashboard. Its purpose is to provide a single, comprehensive reference point for users to understand and effectively utilize the portal's capabilities, ensuring a consistent and guided experience across all features. Highlights
🧠 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. Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive and well-structured documentation page for the Customer Dashboard. The new guide is detailed, clearly written, and accurately reflects the features present in the application code, following the style of existing documentation. I have provided a few minor suggestions to enhance consistency in terminology throughout the document. Overall, this is an excellent and valuable addition.
|
|
||
| #### 3.4.1 Metrics tab | ||
|
|
||
| - View-by segmentation (Model, Project) with time-range selection. |
|
|
||
| - Summary cards for total spend, total tokens, and total requests against quotas. | ||
| - Current plan visibility with billing period metadata. | ||
| - Project and time-range selectors (1d/7d/30d/90d). |
|
|
||
| - Summary cards for total events, failed actions, and resources modified. | ||
| - Search by resource name/user/ID, action filter, resource filter, and date range filter. | ||
| - Clear filters control and export-to-CSV action. |
Motivation
docs/models/models.mdx.Description
docs/customer-dashboard/customer-dashboard.mdxdescribing the portal, USPs, features, how-to guides and FAQ.Testing
pre-commit run --all-files, frontend checksnpm run lint/npm run typecheckin affected frontends, and validate docs build if your CI includes a docs staging step (e.g., site build).Codex Task