docs-v2/content/shared
Jason Stirnaman 8efbd44a2d docs(influxdb3): use shared Grafana docs for all v3 products, fix product and token naming
- Update Core and Enterprise to use shared v3-process-data/visualize/grafana.md
- Fix product name references to use proper {{% product-name %}} shortcode
- Correct token terminology (admin token, database token) across products
- Add HTTP/2 requirement note for SQL queries through Grafana (uses Flight SQL/gRPC)
- Update Flight client library reference to clarify gRPC and Arrow Flight
- Reorganize Grafana screenshot files to use /influxdb/ directory
- Add Cloud Serverless InfluxQL screenshot
2025-10-04 17:36:04 -05:00
..
influxctl Release influxctl v2.10.5 (#6417) 2025-09-23 13:34:34 -06:00
influxdb-client-libraries-reference docs(influxdb3): use shared Grafana docs for all v3 products, fix product and token naming 2025-10-04 17:36:04 -05:00
influxdb-v2 docs(influxdb3): use shared Grafana docs for all v3 products, fix product and token naming 2025-10-04 17:36:04 -05:00
influxdb3 fix(influxdb3): remove get-started/multi-server.md. It's now under install/ 2025-06-24 17:30:49 -05:00
influxdb3-admin InfluxDB 3.4 offline tokens (#6346) 2025-08-28 07:03:03 -06:00
influxdb3-api-reference fix: LInks and headings. Replace `latest` with `v2`. Specify OSS v2 in headings. Closes fix(api-refs): specify v2 in InfluxDB OSS headings #5866, Closes Flux docs: replace `/influxdb/latest` with `/influxdb/v2` #5864. Linting cleanup, removing terminal prompt from examples 2025-02-27 17:50:16 -06:00
influxdb3-cli chore: add 3.5 release notes and config options (#6428) 2025-09-30 09:20:07 -05:00
influxdb3-get-started feat(influxdb3): add plugin library with comprehensive plugin documentation: 2025-07-30 10:16:23 -05:00
influxdb3-internals-reference feat(mono): 3.1 admin tokens: 2025-05-28 22:41:03 -05:00
influxdb3-plugins chore: add 3.5 release notes and config options (#6428) 2025-09-30 09:20:07 -05:00
influxdb3-query-guides fix: links containing hostname 2025-08-24 21:32:26 -05:00
influxdb3-reference chore(monolith): Move telemetry reference to shared/influxdb3-reference. Revise description, disable, and product names. 2025-08-14 14:41:05 -05:00
influxdb3-sample-data InfluxDB 3 Explorer 1.2 (#6350) 2025-08-29 08:44:59 -06:00
influxdb3-visualize Update content/shared/influxdb3-visualize/grafana.md 2025-10-03 14:23:26 -07:00
influxdb3-write-guides Apply suggestions from code review 2025-08-12 09:32:51 -05:00
influxql-v3-reference add influxql integral function (#6236) 2025-08-08 09:50:35 -05:00
sql-reference chore(sql): adds new syntax for sql approx functions (#6402) 2025-10-02 16:15:38 -06:00
v3-core-enterprise-release-notes chore: add 3.5 release notes and config options (#6428) 2025-09-30 09:20:07 -05:00
v3-distributed-admin-custom-partitions Apply suggestions from code review 2025-05-09 10:22:47 -05:00
v3-distributed-internals-reference fix(v3): Apply code review suggestions\ 2025-09-09 14:03:44 -05:00
v3-process-data/visualize docs(influxdb3): use shared Grafana docs for all v3 products, fix product and token naming 2025-10-04 17:36:04 -05:00
README.md chore(v3): Migrate admin/custom-partitioning to shared content 2025-01-09 10:22:12 -06:00
_index.md chore(v3): Migrate admin/custom-partitioning to shared content 2025-01-09 10:22:12 -06:00
v3-line-protocol.md fix: add note to distributed about duplicate points on flush (#6330) 2025-08-22 11:08:48 -06:00

README.md

Shared content

This section is for content shared across multiple products and versions. The /shared/_index.md frontmatter, marks the /shared directory and its children as draft so they don't get rendered when the site is built, but the contents of each shared documented is included in pages that use the file as a source in their frontmatter.

Use shared content

  1. Create a new folder for the content in the content/shared/ directory.

  2. Copy the markdown files into the new folder.

  3. Remove the frontmatter from the markdown files in the shared directory. If the first line starts with a shortcode, add an HTML comment before the first line, otherwise hugo will err.

  4. In each of the files that use the shared content, add a source to the frontmatter that points to the shared markdown file—for example:

    source: /shared/influxql-v3-reference/regular-expressions.md
    
  5. In the doc body, remove the shared Markdown text and add a comment that points to the shared file, in case someone happens upon the page in the repo--for example, in /content/3/core/reference/influxql/regular-expressions.md, add the following: