Create structured approach for managing recurring documentation tasks: Benefits: - Claude can easily reference plans via @plans/[task]/plan-[version].md - Version-controlled plans alongside code for iteration tracking - Progress tracking with execution logs for lessons learned - Reusable templates for recurring documentation patterns - Organized structure for multiple concurrent documentation tasks Usage Examples: - "Claude, execute Phase 1 of @plans/cli-docs-sync/plan-v3.2.0.md" - "Claude, create plan-v3.3.0.md based on previous plan and new release notes" - Create similar structures for other recurring documentation tasks Includes comprehensive CLI documentation sync plan for v3.2.0 with: - Analysis of existing CLI docs and v3.2.0 changes - Specific file paths for updates (retention periods, license management) - Automation strategy for future releases - Phase-based execution approach 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .ci | ||
| .circleci | ||
| .github | ||
| .husky/_ | ||
| .vscode | ||
| api-docs | ||
| assets | ||
| build-scripts | ||
| config | ||
| content | ||
| cypress | ||
| data | ||
| deploy | ||
| flux-build-scripts | ||
| helper-scripts | ||
| influxdb3cli-build-scripts | ||
| layouts | ||
| plans | ||
| resources | ||
| shared/text | ||
| static | ||
| telegraf-build | ||
| test | ||
| .editorconfig | ||
| .frontmatter-schema.json | ||
| .gitignore | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc.yaml | ||
| .s3deploy.yml | ||
| .vale.ini | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| DOC_GPT_PROFILE.md | ||
| Dockerfile.pytest | ||
| Dockerfile.tests | ||
| LICENSE | ||
| PLATFORM_REFERENCE.md | ||
| README.md | ||
| compose.yaml | ||
| cypress.config.js | ||
| eslint.config.js | ||
| hugo_stats.json | ||
| install-influxdb3-core.sh | ||
| lefthook.yml | ||
| package.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.
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.123.8.
-
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.