* feat(askai): add Kapa.ai source group filtering for InfluxDB v3 - Add ai_source_group_ids field to all InfluxDB v3 products in data/products.yml - Add getProductSourceGroupIds() function to retrieve source group IDs from product data - Enables filtered AI responses using Kapa source groups for documentation pages - Follows existing pattern for dynamic product configuration - Implement version-specific config support (__v1, __v2 suffixes) - Append version hints to example questions for InfluxDB database products only - Make example questions generic (remove product-specific names) - Tools (Telegraf, Chronograf, Kapacitor, Flux, Explorer) display questions without version hints - Pre-fills chat input with [version: /path/] for InfluxDB database products - Users can easily edit or remove the pre-filled text - Works for manual opens (Cmd+K) and programmatic opens - Converts module to TypeScript * refactor(ask-ai): change version format to 'My version: <product name>' Use human-readable product names instead of URL paths for better UX. Example: 'My version: InfluxDB 3 Core' instead of '[version: /influxdb3/core/]' * fix(ask-ai): restore working Kapa.open() pre-fill implementation - Replace textarea detection with direct Kapa.open() call - Add Kapa preinitialization code - Use click handler on .ask-ai-open button with capture phase - Handle conversation reset event to re-fill version context - Remove console logging for cleaner production code * fix(ask-ai): remove parentheses from example questions for consistency Make example question format match the pre-fill format: - Before: 'question (My version: product)' - After: 'question My version: product' This ensures users don't think there's a difference between the two formats. * fix(askai): add Explorer product mapping for Ask AI widget - Add influxdb3_explorer mapping to getCurrentProductData() - Add explorer context to getContext() function - Ensures Explorer pages use correct ai_sample_questions from products.yml - Reorder Explorer questions with 'install and run' first This fixes the issue where Explorer Ask AI widget was showing wrong example questions by properly loading the influxdb3_explorer config. * test(page-context): add comprehensive e2e tests for product mappings Add Cypress tests to validate page-context.js correctly identifies: - Product context values for all InfluxDB products - Product data from products.yml configuration - Version information - AI sample questions and source group IDs - Placeholder host values Tests cover: - InfluxDB 3 (Core, Enterprise, Explorer, Cloud variants, Clustered) - InfluxDB v2 and v1 - InfluxDB Cloud (TSM) - Tools (Telegraf, Chronograf, Kapacitor, Flux) Validates the fix for Explorer Ask AI showing correct example questions. Related to #jts-askai-group-filters branch work. * feat(test): add --no-mapping flag to e2e test runner Allow running functionality tests without requiring content file paths. The --no-mapping flag skips content-to-URL mapping, making it easier to run tests that don't depend on specific content files. Usage: # With content mapping (for content-specific tests) node run-e2e-specs.js content/influxdb3/core/_index.md # Without content mapping (for functionality tests) node run-e2e-specs.js --spec cypress/e2e/page-context.cy.js --no-mapping Benefits: - Simplifies running functionality tests like page-context.cy.js - Reduces test startup time by skipping unnecessary file mapping - Makes test commands clearer about their purpose The page-context test was updated to work correctly with this flag. * deps: update caniuse and related hook files * test: Add a `--no-mapping` flag to run tests without specific content files (i.e., test contains all the URLs it needs) * chore(ask-ai): Format example questions * test(page-context): add comprehensive e2e tests for all products in products.yml - Expanded test suite from 6 to 27 tests covering all products - Added tests for InfluxDB 3 products (Explorer, Core, Enterprise, Cloud Serverless, Cloud Dedicated, Clustered) - Added tests for InfluxDB v2 and Cloud (TSM) - Added tests for InfluxDB v1 and Enterprise v1 - Added tests for other products (Telegraf, Chronograf, Kapacitor, Flux) - Validates page mappings in page-context.js - Validates AI sample questions configuration in products.yml - All 27 tests passing * fix(page-context): correct enterprise_influxdb URL pattern matching - Changed pattern from /enterprise_v1/ to /enterprise_influxdb/ - Fixes Ask AI example questions not showing correctly for Enterprise v1 - Pattern now matches actual URL structure /enterprise_influxdb/v1/ - All 27 e2e tests passing * test(page-context): add UI validation for Ask AI widget configuration - Added 4 tests checking Kapa widget script data attributes - Tests verify data-modal-example-questions contains correct product-specific questions - Validates Explorer, Core, Enterprise, and Enterprise v1 configurations - All 31 tests passing (27 existing + 4 new UI tests) * feat(ask-ai): add help in Ask AI widget placeholder - InfluxDB placeholder recommends specifying product and version - Fix page-context.js to use products.influxdb_cloud instead of products.cloud - Add UI tests verifying version-specific naming in Kapa widget script tags * feat(ask-ai): Tailors placeholder for each version/product. Disables "Viewing <product>" in disclaimer note. |
||
|---|---|---|
| .ci | ||
| .circleci | ||
| .claude | ||
| .context | ||
| .github | ||
| .husky/_ | ||
| .vscode | ||
| api-docs | ||
| assets | ||
| config | ||
| content | ||
| cypress | ||
| data | ||
| deploy | ||
| flux-build-scripts | ||
| helper-scripts | ||
| layouts | ||
| scripts | ||
| shared/text | ||
| static | ||
| telegraf-build | ||
| test | ||
| .editorconfig | ||
| .frontmatter-schema.json | ||
| .gitignore | ||
| .mcp.json | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc.yaml | ||
| .remarkrc.yaml | ||
| .s3deploy.yml | ||
| .vale-instructions.ini | ||
| .vale.ini | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| DOCS-CONTRIBUTING.md | ||
| DOCS-FRONTMATTER.md | ||
| DOCS-SHORTCODES.md | ||
| DOCS-TESTING.md | ||
| Dockerfile.pytest | ||
| Dockerfile.tests | ||
| LICENSE | ||
| PLATFORM_REFERENCE.md | ||
| README.md | ||
| broken_links_report.json | ||
| compose.yaml | ||
| cypress.config.js | ||
| eslint.config.js | ||
| hugo_stats.json | ||
| install-influxdb3-core.sh | ||
| install_influxdb3.sh | ||
| lefthook.yml | ||
| package.json | ||
| tsconfig.json | ||
| yarn.lock | ||
README.md
InfluxData Product Documentation
This repository contains the InfluxData product documentation for InfluxDB and related tooling published at docs.influxdata.com.
Contributing
We welcome and encourage community contributions. For information about contributing to the InfluxData documentation, see Contribution guidelines.
Testing
For information about testing the documentation, including code block testing, link validation, and style linting, see Testing guide.
Documentation Tools
This repository includes a docs CLI tool for common documentation workflows:
# Create new documentation from a draft
npx docs create drafts/new-feature.md --products influxdb3_core
# Edit existing documentation from a URL
npx docs edit https://docs.influxdata.com/influxdb3/core/admin/
# Add placeholder syntax to code blocks
npx docs placeholders content/influxdb3/core/admin/upgrade.md
# Get help
npx docs --help
The docs command is automatically configured when you run yarn install.
Documentation
Comprehensive reference documentation for contributors:
- Contributing Guide - Workflow and contribution guidelines
- Shortcodes Reference - Complete Hugo shortcode documentation
- Working examples - Test shortcodes in the browser
- Frontmatter Reference - Complete page metadata documentation
- Testing Guide - Testing procedures and requirements
- API Documentation - API reference generation
Quick Links
Reporting a Vulnerability
InfluxData takes security and our users' trust very seriously. If you believe you have found a security issue in any of our open source projects, please responsibly disclose it by contacting security@influxdata.com. More details about security vulnerability reporting, including our GPG key, can be found at https://www.influxdata.com/how-to-report-security-vulnerabilities/.
Running the docs locally
-
Clone this repository to your local machine.
-
Install NodeJS, Yarn, Hugo, & Asset Pipeline Tools
The InfluxData documentation uses Hugo, a static site generator built in Go. The site uses Hugo's asset pipeline, which requires the extended version of Hugo along with NodeJS tools like PostCSS, to build and process stylesheets and JavaScript.
To install the required dependencies and build the assets, do the following:
-
In your terminal, from the
docs-v2directory, install the dependencies:cd docs-v2 yarn installNote: The most recent version of Hugo tested with this documentation is 0.149.0.
After installation, the
docscommand will be available vianpx:npx docs --help
-
To generate the API docs, see api-docs/README.md.
-
Start the Hugo server
Hugo provides a local development server that generates the HTML pages, builds the static assets, and serves them at
localhost:1313.In your terminal, start the Hugo server:
npx hugo server -
View the docs at localhost:1313.
Alternative: Use docker compose
-
Clone this repository to your local machine. See how to clone a repository.
-
Follow the instructions to install Docker Desktop and Docker Compose to your local machine.
-
Use Docker Compose to start the Hugo server in development mode--for example, enter the following command in your terminal:
docker compose up local-dev -
View the docs at localhost:1313.