* feat(ci): improve linting configuration for instruction files - Add GitHub-flavored Markdown support with remark-gfm - Create generic Vale config (.vale-instructions.ini) for instruction files - Use pattern-based file inclusion instead of explicit file lists - Mount repository to /workdir in remark-lint container to preserve node_modules Changes: - Add remark-gfm to .ci/remark-lint/package.json - Create .remarkrc.yaml at repository root for instruction files - Update content/.remarkrc.yaml to include remark-gfm - Create .vale-instructions.ini for generic writing rules - Update compose.yaml: mount repo to /workdir (preserves /app/node_modules) - Update lefthook.yml: use glob patterns for uppercase .md files and .github/**/*.md - Update DOCS-CONTRIBUTING.md: remove empty CONTRIBUTING.md directory reference Benefits: - Automatic inclusion of new instruction files without config updates - Pattern matching for uppercase .md files (DOCS-*.md, CLAUDE.md, etc.) - Coverage for .github/, .claude/, api-docs/ directories - GFM features: tables, task lists, strikethrough, autolinks, footnotes - Separate linting rules for instruction files vs product documentation feat(lint): separate remark-lint auto-fix for instructions vs report-only for content - Split lint-markdown into two hooks: - lint-markdown-instructions: Auto-fixes README, DOCS-*.md, .github/**, .claude/** - lint-markdown-content: Reports issues in content/**, api-docs/** without modifying - Changed remark-lint volume mount from read_only: true to read_only: false - Instruction files now behave like Prettier (auto-fix + stage) - Content files report errors and block commits until manually fixed * chore(instructions): Add content/shared details, husky/lefthook updates |
||
|---|---|---|
| .ci | ||
| .circleci | ||
| .claude | ||
| .context | ||
| .github | ||
| .husky/_ | ||
| .vscode | ||
| api-docs | ||
| assets | ||
| config | ||
| content | ||
| cypress | ||
| data | ||
| deploy | ||
| flux-build-scripts | ||
| helper-scripts | ||
| layouts | ||
| plans/cli-docs-sync | ||
| 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
InfluxDB 2.0 Documentation
This repository contains the InfluxDB 2.x documentation 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
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.
-
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.