Merge pull request #8346 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-devops-docs (branch main)

Author: Albertyang0

docs/project/wiki/wiki-file-structure.md

@@ -8,7 +8,7 @@ ms.topic: concept-article
 ms.author: chcomley
 ms.reviewer: gopinach
 author: chcomley
-ms.date: 05/29/2025
+ms.date: 09/25/2025
 #customer intent: As an Azure DevOps developer, I want to understand the wiki file and folder structure in the Git repository, so I can follow the naming and location conventions.
 ---
 
@@ -48,6 +48,20 @@ The file name for each wiki page corresponds to the wiki page title. In the file
 
 The _.order_ file defines the wiki page sequence. Git looks for this file in each folder to identify the sequence to present files at that location. The default page sequence is alphabetical order (A to Z) by file name.
 
+> [!IMPORTANT]
+> When a parent folder contains only subfolders and no files of its own, the wiki displays the parent folder as blank—even if the subfolders include markdown files. To ensure visibility of markdown files within subfolders, always place at least one file (such as a `.order` file or any other file with content) in the parent folder.
+>
+>```
+>|- parent-folder
+>|-- sub-folder1
+>|   |-- file1.md
+>|   |-- file2.md
+>|-- sub-folder2
+>|   |-- file3.md
+>|   |-- file4.md
+>|-- .order
+>```
+
 ### Define custom page sequence
 
 When a folder doesn't have an _.order_ file, Git uses the default alphabetical sequence.
@@ -89,4 +103,4 @@ If a folder has a custom sequence, you can revert the sort method to alphabetica
 
 - [Set up wiki vs. publish code as wiki](provisioned-vs-published-wiki.md)
 - [Create a wiki for your team project](wiki-create-repo.md)
-- [Publish a Git repository to a wiki](publish-repo-to-wiki.md)
+- [Publish a Git repository to a wiki](publish-repo-to-wiki.md)