Document additional DateTimeOffset translations

.gitattributes

@@ -0,0 +1,2 @@
+* text=auto
+*.sh text eol=lf

.github/ISSUE_TEMPLATE/a-general-issue.yml

@@ -0,0 +1,13 @@
+name: "General feedback"
+description: Provide general feedback about the Entity Framework docs or a specific article.
+body:
+  - type: markdown
+    attributes:
+      value: "Describe the issue or suggestion. NOTE: If your issue is about a specific article, it's best to submit your feedback by clicking the 'Open a documentation issue' link in the 'EntityFramework feedback' box at the end of the article."
+  - type: input
+    id: topic
+    attributes:
+      label: Issue or suggestion
+      description: Describe the issue
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Entity Framework product feedback
+    url: https://github.com/dotnet/efcore/issues
+    about: Log Entity Framework product feedback here
+  - name: learn.microsoft.com site feedback
+    url: https://github.com/MicrosoftDocs/feedback/issues/new/choose
+    about: Log general learn.microsoft.com site issues here

.github/ISSUE_TEMPLATE/z-customer-feedback.yml

@@ -0,0 +1,64 @@
+name: Learn feedback control.
+description: |
+  ⛔ This template is hooked into the feedback control on the bottom of every page on the live site. It automatically fills in several fields for you. Don't use for other purposes. ⛔
+body:
+  - type: markdown
+    attributes:
+      value: "## Issue information"
+  - type: markdown
+    attributes:
+      value: Select the issue type, and describe the issue in the text box below. Add as much detail as needed to help us resolve the issue.
+  - type: dropdown
+    id: issue-type
+    attributes:
+      label: Type of issue
+      options:
+        - Typo
+        - Code doesn't work
+        - Missing information
+        - Outdated article
+        - Other (describe below)
+    validations:
+      required: true
+  - type: textarea
+    id: feedback
+    validations:
+      required: true
+    attributes:
+      label: Description
+  - type: markdown
+    attributes:
+      value: "## 🚧 Article information 🚧"
+  - type: markdown
+    attributes:
+      value: "*Don't modify the following fields*. They are automatically filled in for you. Doing so will disconnect your issue from the affected article. *Don't edit them*."
+  - type: input
+    id: pageUrl
+    validations:
+      required: true
+    attributes:
+      label: Page URL
+  - type: input
+    id: contentSourceUrl
+    validations:
+      required: true
+    attributes:
+      label: Content source URL
+  - type: input
+    id: documentVersionIndependentId
+    validations:
+      required: true
+    attributes:
+      label: Document Version Independent Id
+  - type: input
+    id: platformId
+    validations:
+      required: true
+    attributes:
+      label: Platform Id
+  - type: input
+    id: author
+    validations:
+      required: true
+    attributes:
+      label: Article author

.github/agents/docs-generator.agent.md

@@ -0,0 +1,36 @@
+---
+name: EF Documentation Generator
+description: This agent creates documentation PRs in the EF documentation site when new features are implemented in EF Core.
+disable-model-invocation: true
+---
+
+# Document new EF features
+
+Given an EF issue by the user, this custom agent generates documentation for features introduced in that issue and submits a PR to the EF docs repo (dotnet/EntityFramework.Docs).
+
+## Target branch
+
+* The EF repo has automation to automatically add a label indicating in which preview/rc the feature has been completed; the label is applied to the issue (not PR), and has the form `preview-3` or `rc-2` with the number adjusted.
+* The docs repo should have a corresponding branch, containing documentation to be published live when that preview/rc is published.
+* When the workflow is launched, check the issue, find the preview/rc label, and submit the PR against the corresponding branch in the doc repo (dotnet/EntityFramework.Docs).
+* If the label is missing, abort and post a comment to the triggering issue.
+
+## Writing the documentation
+
+* Fully read the conversation history of the issue, as well as any linked PRs or relevant issues linked from it, to gain good context on the feature, APIs introduced, etc.
+* Add documentation in the appropriate section of the docs, depending on what the feature is.
+* Fully document the feature, but keep it brief - do not add edge-case, non-important documentation in the name of exhaustivity that wouldn't be relevant to the majority of users.
+* Before the new documentation, add the following note (adjusting for the major version):
+
+```
+> [!NOTE]
+> This feature is being introduced in EF Core 11, which is currently in preview.
+```
+
+* Find the "what's new" page for the latest major release (typically `core/what-is-new/ef-core-11.0`, adjusting for the version), and add a **brief** section on the feature - just the minimum needed to make the user understand what it's about; include a minimal code sample as well if relevant. At the bottom, add a line such as "For more information on X, see the documentation" linking to the full docs added above, in case the user wants to dive deeper.
+* For both the full docs and the what's new documentation, do not simply create a new section; first check to see if there's an existing section that already covers related/similar functionality; if there is, either merge the new content into it or place the new section next to it.
+* If the issue adds a function translation, add the appropriate entry (or entries) in the provider's functions page. Do not add functions entries for LINQ operators (e.g. `Contains`).
+
+## Additional instructions
+
+* The commit in the resulting PR should have a title of the form "Document X", where X is the name of the feature as it appears in the title of the originating issue. If the title is too long for a git commit, make it shorter. The commit body should be of the form "Document Y", where Y is a link to the originating issue.

.github/copilot-instructions.md

@@ -0,0 +1,153 @@
+# Copilot Instructions for EntityFramework.Docs
+
+## Repository Overview
+
+This repository contains the **Entity Framework Core (EF Core) and Entity Framework 6 (EF6) documentation** published at <https://learn.microsoft.com/ef/>. It is a **documentation-focused repository** with markdown documentation files and C# code samples.
+
+**Key Technologies:**
+- **Documentation**: Markdown, DocFX, Microsoft Learn publishing platform
+- **Samples**: Latest public release of .NET, C#, Entity Framework Core/EF6, SQL Server, SQLite, Cosmos DB
+
+## Critical Build & Validation Instructions
+
+### Prerequisites
+- **.NET SDK** (latest public release) is required (check with `dotnet --version`)
+- **Node.js** for markdown linting (check with `node --version`)
+
+### Markdown Linting (ALWAYS RUN BEFORE COMMITTING)
+
+**Command:**
+```bash
+npm i -g markdownlint-cli
+markdownlint "**/*.md" -i "entity-framework/ef6/"
+```
+
+**Configuration:** `.markdownlint.json` at repo root
+**Key Rules:** MD046 (fenced code blocks), MD025 (single H1 with front matter)
+**CI Workflow:** `.github/workflows/markdownlint.yml` runs on all PRs with markdown changes
+**IMPORTANT:** EF6 documentation (`entity-framework/ef6/`) is excluded from linting
+
+### Building Code Samples
+
+**Location:** All samples are in `samples/` directory
+- `samples/core/` - EF Core samples
+- `samples/end2end/PlanetaryDocs/` - Complete end-to-end Blazor application
+
+Samples are standard .NET projects. Build them with:
+```bash
+cd samples/end2end/PlanetaryDocs
+dotnet build
+```
+
+Or build all core samples:
+```bash
+cd samples/core
+dotnet build
+```
+
+**CI Workflow:** `.github/workflows/build-samples.yml` runs on PRs to `live` branch with changes to `samples/`
+
+## Repository Structure
+
+### Documentation
+```
+entity-framework/
+├── docfx.json           # DocFX configuration
+├── core/                # EF Core documentation
+├── ef6/                 # EF6 documentation (excluded from markdownlint)
+├── efcore-and-ef6/      # Comparison and porting guides
+└── breadcrumb/          # Navigation breadcrumbs
+```
+
+### Configuration Files
+- `.markdownlint.json` - Markdown linting rules
+- `.openpublishing.publish.config.json` - Microsoft Learn publishing config
+- `.openpublishing.redirection.json` - URL redirections (update when renaming/moving files)
+- `.github/workflows/markdownlint.yml` - Markdown lint CI
+- `.github/workflows/build-samples.yml` - Sample build CI
+
+### Samples
+```
+samples/
+├── core/                # EF Core samples
+│   ├── Samples.sln      # Solution with all core samples
+│   └── .editorconfig    # Code style rules
+└── end2end/
+    └── PlanetaryDocs/   # Complete Blazor app
+```
+
+## Making Changes
+
+### Documentation Changes
+
+**File Format:** DocFX-flavored Markdown (DFM), superset of GitHub-flavored Markdown (GFM)
+**Style Guide:** <https://learn.microsoft.com/contribute/dotnet/dotnet-style-guide>
+
+**Code Snippet Syntax:**
+- Reference external code files (preferred): `[!code-csharp[Main](../../../samples/core/saving/Program.cs)]`
+- With C# region (always prefer over line ranges): `[!code-csharp[Main](../../../samples/core/saving/Program.cs?name=snippet_Example)]`
+- With highlighting: `[!code-csharp[Main](../../../samples/core/saving/Program.cs?highlight=1-3,10)]`
+
+**Static Content:** Images and files in `_static/` folders within each documentation area
+
+**ALWAYS:**
+1. Ensure code snippets reference actual sample files in `samples/` directory
+2. Run `markdownlint "**/*.md" -i "entity-framework/ef6/"` before committing
+3. Match folder structure: docs in `entity-framework/core/` align with samples in `samples/core/`
+4. When referencing an API, use docfx `<xref>` rather than code fencing to link to the API documentation
+5. When adding, removing or renaming pages, update the `entity-framework/toc.yml` file to make the changes appear in the doc site's table of contents
+6. If renaming or moving files, update `.openpublishing.redirection.json` to add redirects from old URLs
+
+### Sample Code Changes
+
+**ALWAYS:**
+1. Ensure samples build successfully: `cd samples/end2end/PlanetaryDocs && dotnet build`
+2. Follow existing code style (see `samples/core/.editorconfig`)
+3. Use C# regions (`#region snippet_Name`) for code referenced in documentation
+4. When editing samples, verify that documentation referencing those samples still uses correct line numbers for highlighting
+
+**Common Sample Patterns:**
+- Console applications showing specific EF Core features
+- Each sample folder typically has one `.csproj` file
+- Samples use in-memory SQLite or SQL Server LocalDB
+
+## Testing Documentation Locally with DocFX
+
+**DocFX** creates a locally hosted version of the documentation site (without Microsoft Learn styling).
+
+**Requirements:**
+- Windows: .NET Framework + DocFX tool
+- macOS/Linux: Mono + DocFX
+
+**Commands (not regularly used for PRs):**
+```bash
+# Download DocFX from https://github.com/dotnet/docfx/releases
+# Add to PATH, then from repo root:
+docfx entity-framework/docfx.json -t default --serve
+# View at http://localhost:8080
+```
+
+**Note:** DocFX is optional for most contributions. Focus on markdown linting and sample builds.
+
+## Common Pitfalls & Solutions
+
+**Problem:** `samples/core/Samples.sln` build fails with "Resource temporarily unavailable" NuGet errors
+**Solution:** This is a transient network issue with Azure DevOps preview package feeds. Retry the build. If persistent, build individual sample projects instead of the full solution.
+
+**Problem:** Markdownlint errors on legitimate markdown
+**Solution:** Check `.markdownlint.json` for disabled rules. Some rules (MD028, MD033, MD036, MD041) are intentionally disabled for documentation needs.
+
+**Problem:** Code snippet not rendering in documentation
+**Solution:** Verify the referenced file path is correct relative to the .md file location. Ensure C# region names match exactly (case-sensitive).
+
+**Problem:** Changes to EF6 docs trigger linting warnings
+**Solution:** EF6 docs (`entity-framework/ef6/`) are excluded from linting. This is intentional due to legacy content.
+
+## Trust These Instructions
+
+These instructions have been validated by running actual builds, tests, and linting on the repository. Only perform additional exploration if:
+- Information is incomplete or unclear
+- Instructions are found to be incorrect
+- You need details about a specific undocumented area
+
+For quick fixes (typos, grammar), simple markdown edits without building samples are acceptable.

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: nuget
+    directory: /
+    schedule:
+      interval: weekly

.github/workflows/build-samples.yml

@@ -0,0 +1,37 @@
+name: Build Samples
+
+on:
+  push:
+    branches: [live]
+    paths:
+      - "samples/core/**"
+      - "samples/end2end/**"
+      - ".github/workflows/build-samples.yml"
+  pull_request:
+    branches: [live]
+    paths:
+      - "samples/core/**"
+      - "samples/end2end/**"
+      - ".github/workflows/build-samples.yml"
+
+jobs:
+  build:
+    runs-on: ubuntu-24.04
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup .NET 10.0 SDK
+        uses: actions/setup-dotnet@v4
+        with:
+          dotnet-version: 10.0.x
+          include-prerelease: true
+
+      - name: Build samples
+        working-directory: samples/core
+        run: dotnet build
+
+      - name: Build planetary docs sample
+        working-directory: samples/end2end/PlanetaryDocs
+        run: dotnet build

.github/workflows/markdownlint-problem-matcher.json

@@ -0,0 +1,17 @@
+{
+    "problemMatcher": [
+        {
+            "owner": "markdownlint",
+            "pattern": [
+                {
+                    "regexp": "^([^:]*):(\\d+):?(\\d+)?\\s([\\w-\\/]*)\\s(.*)$",
+                    "file": 1,
+                    "line": 2,
+                    "column": 3,
+                    "code": 4,
+                    "message": 5
+                }
+            ]
+        }
+    ]
+}

.github/workflows/markdownlint.yml

@@ -0,0 +1,34 @@
+name: Markdownlint
+
+on:
+  push:
+    paths:
+      - "entity-framework/**/*.md"
+      - "!entity-framework/ef6/**"
+      - ".markdownlint.json"
+      - ".github/workflows/markdownlint.yml"
+      - ".github/workflows/markdownlint-problem-matcher.json"
+  pull_request:
+    paths:
+      - "**/*.md"
+      - "!entity-framework/ef6/**"
+      - ".markdownlint.json"
+      - ".github/workflows/markdownlint.yml"
+      - ".github/workflows/markdownlint-problem-matcher.json"
+
+jobs:
+  lint:
+    runs-on: ubuntu-24.04
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Use Node.js
+      uses: actions/setup-node@v1
+      with:
+        node-version: 20.x
+
+    - name: Run Markdownlint
+      run: |
+        echo "::add-matcher::.github/workflows/markdownlint-problem-matcher.json"
+        npm i -g markdownlint-cli
+        markdownlint "entity-framework/**/*.md" -i "entity-framework/ef6/"