Merge branch 'master' into patch-2

Author: jstirnaman

.context/README.md

@@ -0,0 +1,44 @@
+# Context Files for LLMs and AI Tools 
+
+This directory contains plans, reports, and other context files that are:
+- Used to provide context to LLMs during development
+- Not committed to the repository
+- May be transient or belong in other repositories
+
+## Directory Structure
+
+- `plans/` - Documentation plans and roadmaps
+- `reports/` - Generated reports and analyses
+- `research/` - Research notes and findings
+- `templates/` - Reusable templates for Claude interactions
+
+## Usage
+
+Place files here that you want to reference--for example, using @ mentions in Claude--such as:
+- Documentation planning documents
+- API migration guides
+- Performance reports
+- Architecture decisions
+
+## Example Structure
+
+```
+.context/
+├── plans/
+│   ├── v3.2-release-plan.md
+│   └── api-migration-guide.md
+├── reports/
+│   ├── weekly-progress-2025-07.md
+│   └── pr-summary-2025-06.md
+├── research/
+│   └── competitor-analysis.md
+└── templates/
+    └── release-notes-template.md
+```
+
+## Best Practices
+
+1. Use descriptive filenames that indicate the content and date
+2. Keep files organized in appropriate subdirectories
+3. Consider using date prefixes for time-sensitive content (e.g., `2025-07-01-meeting-notes.md`)
+4. Remove outdated files periodically to keep the context relevant

.github/copilot-instructions.md

@@ -1,13 +1,16 @@
-# GitHub Copilot Instructions for InfluxData Documentation
+# Instructions for InfluxData Documentation
 
 ## Purpose and scope
 
-GitHub Copilot should help document InfluxData products by creating clear, accurate technical content with proper code examples, frontmatter, and formatting.
+Help document InfluxData products by creating clear, accurate technical content with proper code examples, frontmatter, and formatting.
 
 ## Documentation structure
 
 - **Product version data**: `/data/products.yml`
-- **Products**:
+- **InfluxData products**:
+  - InfluxDB 3 Explorer
+    - Documentation source path: `/content/influxdb3/explorer`
+    - Published for the web: https://docs.influxdata.com/influxdb3/explorer/
   - InfluxDB 3 Core
     - Documentation source path: `/content/influxdb3/core`
     - Published for the web: https://docs.influxdata.com/influxdb3/core/
@@ -92,7 +95,8 @@ GitHub Copilot should help document InfluxData products by creating clear, accur
 
 ## Markdown and shortcodes
 
-- Include proper frontmatter for each page:
+- Include proper frontmatter for Markdown pages in `content/**/*.md` (except for
+  shared content files in `content/shared/`):
 
   ```yaml
   title: # Page title (h1)
@@ -180,3 +184,17 @@ Table: keys: [_start, _stop, _field, _measurement]
 ## Related repositories
 
 - **Internal documentation assistance requests**: https://github.com/influxdata/DAR/issues Documentation
+
+## Additional instruction files
+
+For specific workflows and content types, also refer to:
+
+- **InfluxDB 3 code placeholders**: `.github/instructions/influxdb3-code-placeholders.instructions.md` - Guidelines for placeholder formatting, descriptions, and shortcode usage in InfluxDB 3 documentation
+- **Contributing guidelines**: `.github/instructions/contributing.instructions.md` - Detailed style guidelines, shortcode usage, frontmatter requirements, and development workflows
+- **Content-specific instructions**: Check `.github/instructions/` directory for specialized guidelines covering specific documentation patterns and requirements
+
+## Integration with specialized instructions
+
+When working on InfluxDB 3 documentation (Core/Enterprise), prioritize the placeholder guidelines from `influxdb3-code-placeholders.instructions.md`.
+
+For general documentation structure, shortcodes, and development workflows, follow the comprehensive guidelines in `contributing.instructions.md`.