Move terminology docs to docfx/docs per CONTRIBUTING.md guidelines

Co-authored-by: tig <[email protected]>

TERMINOLOGY_DIAGRAMS.md → docfx/docs/terminology-diagrams.md

@@ -320,7 +320,7 @@ The proposed terminology (`Application.Current` and `Application.RunStack`) prov
 ---
 
 **See also:**
-- [TERMINOLOGY_PROPOSAL.md](TERMINOLOGY_PROPOSAL.md) - Complete detailed proposal
-- [TERMINOLOGY_PROPOSAL_SUMMARY.md](TERMINOLOGY_PROPOSAL_SUMMARY.md) - Quick reference
-- [TERMINOLOGY_BEFORE_AFTER.md](TERMINOLOGY_BEFORE_AFTER.md) - Code comparison examples
-- [TERMINOLOGY_INDEX.md](TERMINOLOGY_INDEX.md) - Navigation guide
+- [terminology-proposal.md](terminology-proposal.md) - Complete detailed proposal
+- [terminology-proposal-summary.md](terminology-proposal-summary.md) - Quick reference
+- [terminology-before-after.md](terminology-before-after.md) - Code comparison examples
+- [terminology-index.md](terminology-index.md) - Navigation guide

TERMINOLOGY_INDEX.md → docfx/docs/terminology-index.md

@@ -4,7 +4,7 @@ This directory contains a comprehensive proposal for renaming `Application.Top`
 
 ## 📚 Documents
 
-### 1. [TERMINOLOGY_PROPOSAL_SUMMARY.md](TERMINOLOGY_PROPOSAL_SUMMARY.md) ⭐ **Start Here**
+### 1. [terminology-proposal-summary.md](terminology-proposal-summary.md) ⭐ **Start Here**
 Quick overview of the proposal with key recommendations in a table format. Best for getting a high-level understanding.
 
 **Contents:**
@@ -13,7 +13,7 @@ Quick overview of the proposal with key recommendations in a table format. Best
 - Migration strategy overview
 - Quick code examples
 
-### 2. [TERMINOLOGY_DIAGRAMS.md](TERMINOLOGY_DIAGRAMS.md) 📊 **Visual Diagrams**
+### 2. [terminology-diagrams.md](terminology-diagrams.md) 📊 **Visual Diagrams**
 Mermaid diagrams visualizing the proposal, relationships, and migration path.
 
 **Contents:**
@@ -26,7 +26,7 @@ Mermaid diagrams visualizing the proposal, relationships, and migration path.
 - Evolution path timeline
 - Migration phases Gantt chart
 
-### 3. [TERMINOLOGY_BEFORE_AFTER.md](TERMINOLOGY_BEFORE_AFTER.md) 📝 **Code Examples**
+### 3. [terminology-before-after.md](terminology-before-after.md) 📝 **Code Examples**
 Side-by-side comparisons showing how the new terminology improves code clarity.
 
 **Contents:**
@@ -36,7 +36,7 @@ Side-by-side comparisons showing how the new terminology improves code clarity.
 - Consistency with .NET patterns
 - Summary comparison table
 
-### 4. [TERMINOLOGY_PROPOSAL.md](TERMINOLOGY_PROPOSAL.md) 📖 **Full Details**
+### 4. [terminology-proposal.md](terminology-proposal.md) 📖 **Full Details**
 Complete, comprehensive proposal with all analysis, rationale, and implementation details.
 
 **Contents:**
@@ -71,11 +71,11 @@ Complete, comprehensive proposal with all analysis, rationale, and implementatio
 
 **If you want to...**
 
-- 📋 **Get the gist quickly**: Read [TERMINOLOGY_PROPOSAL_SUMMARY.md](TERMINOLOGY_PROPOSAL_SUMMARY.md)
-- 🎨 **See visual diagrams**: Read [TERMINOLOGY_DIAGRAMS.md](TERMINOLOGY_DIAGRAMS.md)
-- 👀 **See concrete examples**: Read [TERMINOLOGY_BEFORE_AFTER.md](TERMINOLOGY_BEFORE_AFTER.md)
-- 🔍 **Understand all details**: Read [TERMINOLOGY_PROPOSAL.md](TERMINOLOGY_PROPOSAL.md)
-- 💡 **Implement the changes**: See implementation checklist in [TERMINOLOGY_PROPOSAL.md](TERMINOLOGY_PROPOSAL.md)
+- 📋 **Get the gist quickly**: Read [terminology-proposal-summary.md](terminology-proposal-summary.md)
+- 🎨 **See visual diagrams**: Read [terminology-diagrams.md](terminology-diagrams.md)
+- 👀 **See concrete examples**: Read [terminology-before-after.md](terminology-before-after.md)
+- 🔍 **Understand all details**: Read [terminology-proposal.md](terminology-proposal.md)
+- 💡 **Implement the changes**: See implementation checklist in [terminology-proposal.md](terminology-proposal.md)
 
 ## 🔗 Related Issues
 

TERMINOLOGY_PROPOSAL_SUMMARY.md → docfx/docs/terminology-proposal-summary.md

@@ -1,6 +1,6 @@
 # Terminology Proposal Summary
 
-This is a brief summary of the [full terminology proposal](TERMINOLOGY_PROPOSAL.md).
+This is a brief summary of the [full terminology proposal](terminology-proposal.md).
 
 ## Recommended Changes
 
@@ -54,9 +54,9 @@ var focused = Application.Current.MostFocused;
 
 ## See Also
 
-- [Visual Diagrams](TERMINOLOGY_DIAGRAMS.md) - Mermaid diagrams visualizing the proposal
-- [Full Proposal Document](TERMINOLOGY_PROPOSAL.md) - Complete analysis and implementation details
-- [Before/After Examples](TERMINOLOGY_BEFORE_AFTER.md) - Side-by-side code comparisons
-- [Documentation Index](TERMINOLOGY_INDEX.md) - Navigation guide
+- [Visual Diagrams](terminology-diagrams.md) - Mermaid diagrams visualizing the proposal
+- [Full Proposal Document](terminology-proposal.md) - Complete analysis and implementation details
+- [Before/After Examples](terminology-before-after.md) - Side-by-side code comparisons
+- [Documentation Index](terminology-index.md) - Navigation guide
 - Issue #4329 - Original issue requesting terminology improvements
 - Issue #2491 - Toplevel refactoring and `IRunnable` interface work

docfx/docs/toc.yml

@@ -26,6 +26,8 @@
   href: events.md
 - name: Lexicon & Taxonomy
   href: lexicon.md
+- name: Terminology Proposal
+  href: terminology-index.md
 - name: Keyboard
   href: keyboard.md
 - name: Layout Engine