Create and edit InfluxData docs
Learn how to create and edit InfluxData documentation.
- Submit an issue to request new or updated documentation
- Edit an existing page in your browser
- Create and edit locally with the docs-v2 repository
- Helpful resources
Submit an issue to request new or updated documentation
- Public: https://github.com/influxdata/docs-v2/issues/
- Private: https://github.com/influxdata/DAR/issues/
Edit an existing page in your browser
Example: Editing a product-specific page
- Visit https://docs.influxdata.com public docs
- Search, Ask AI, or navigate to find the page to edit–for example, https://docs.influxdata.com/influxdb3/cloud-serverless/get-started/
- Click the “Edit this page” link at the bottom of the page. This opens the GitHub repository to the file that generates the page
- Click the pencil icon to edit the file in your browser
- Commit and create a pull request
Create and edit locally with the docs-v2 repository
Use docs scripts with AI agents to help you create and edit documentation locally, especially when working with shared content for multiple products.
Prerequisites:
Clone or fork the docs-v2 repository:
git clone https://github.com/influxdata/docs-v2.git cd docs-v2Run
yarnin the repository root to install dependenciesOptional: Set up GitHub CLI
To run and test your changes locally, enter the following command in your terminal:
yarn hugo serverTo refresh shared content after making changes, touch or edit the frontmatter file, or stop the server (Ctrl+C) and restart it.
To list all available scripts, run:
yarn runEdit an existing page locally
Use the npx docs edit command to open an existing page in your editor.
npx docs edit https://docs.influxdata.com/influxdb3/enterprise/get-started/Create content locally
Use the npx docs create command with your AI agent tool to scaffold frontmatter and generate new content.
- The
npx docs createcommand accepts draft input from stdin or from a file path and generates a prompt file from the draft and your product selections - The prompt file makes AI agents aware of InfluxData docs guidelines, shared content, and product-specific requirements
npx docs createis designed to work automatically withclaude, but you can use the generated prompt file with any AI agent (for example,copilotorcodex)
docs-v2 contains custom configuration for agents like Claude and Copilot Agent mode.
Generate content and frontmatter from a draft
Open a Claude Code prompt:
claude codeIn the prompt, run the
docs createcommand with the path to your draft file. Optionally, include the--productsflag and product namespaces to preselect products–for example:npx docs create .context/drafts/"Upgrading Enterprise 3 (draft).md" \ --products influxdb3_enterprise,influxdb3_coreIf you don’t include the
--productsflag, you’ll be prompted to select products after running the command.
The script first generates a prompt file, then the agent automatically uses it to generate content and frontmatter based on the draft and the products you select.
Use npx docs create to generate a prompt file and then pipe it to your preferred AI agent.
Include the --products flag and product namespaces to preselect products
The following example uses Copilot to process a draft file:
npx docs create .context/drafts/"Upgrading Enterprise 3 (draft).md" \
--products "influxdb3_enterprise,influxdb3_core" | \
copilot --prompt --allow-all-toolsReview, commit, and create a pull request
After you create or edit content, test and review your changes, and then create a pull request.
Check AI-generated content
Always review and validate AI-generated content for accuracy. Make sure example commands are correct for the version you’re documenting.
Test and review your changes
Run a local Hugo server to preview your changes:
yarn hugo serverVisit http://localhost:1313 to review your changes in the browser.
If you need to preview changes in a live production-like environment that you can also share with others, the Docs team can deploy your branch to the staging site.
Commit and create a pull request
- Commit your changes to a new branch
- Fix any issues found by automated checks
- Push the branch to your fork or to the docs-v2 repository
git add content
git commit -m "feat(product): Your commit message"
git push origin your-branch-nameCreate a pull request
- Create a pull request against the
masterbranch of the docs-v2 repository - Add reviewers:
@influxdata/docs-team- team members familiar with the product area
- Optionally, assign Copilot to review
- After approval and automated checks are successful, merge the pull request (if you have permissions) or wait for the docs team to merge it.
- Visit influxdata/docs-v2 pull requests on GitHub
- Optional: edit PR title and description
- Optional: set to draft if it needs more work
- When ready for review, assign
@influxdata/docs-teamand other reviewers
gh pr create \
--base master \
--head your-branch-name \
--title "Your PR title" \
--body "Your PR description" \
--reviewer influxdata/docs-team,<other-reviewers>Other resources
DOCS-*.md: Documentation standards and guidelines- http://localhost:1313/example/: View shortcode examples
- https://app.kapa.ai: Review content gaps identified from Ask AI answers
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.