Merge branch 'main' into GHI-1891

Author: sachinkaushik

.github/workflows/docs-reusable-workflow.yaml

@@ -2,9 +2,9 @@
 # SPDX-FileCopyrightText: (C) 2025 Intel Corporation
 # SPDX-License-Identifier: Apache-2.0
 
-name: 'Build Documentation'
+name: "Build Documentation"
 
-on:  # yamllint disable-line rule:truthy rule:line-length
+on: # yamllint disable-line rule:truthy rule:line-length
   workflow_call:
     inputs:
       docs_directory:
@@ -33,14 +33,13 @@ permissions:
 jobs:
   build-documentation:
     permissions:
-      contents: read        # minimal privilege required
+      contents: read # minimal privilege required
     runs-on: ubuntu-latest
     env:
       DOCS_DIR: ${{ inputs.docs_directory }}
     steps:
-
       - name: Checkout code
-        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8  # v5.0.0
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
         with:
           # Fetch all history, otherwise sporadic issue with missing tags
           fetch-depth: 0

.github/workflows/documentation-check.yaml

@@ -1,7 +1,7 @@
 
 # Edge-AI-Suites Contributor Guide
 
-The following are guidelines for contributing to the Edge AI Suites project, including the code of conduct, submitting issues, and contributing code.  
+The following are guidelines for contributing to the Edge AI Suites project, including the code of conduct, submitting issues, and contributing code.
 
 # Table of Contents
 
@@ -15,37 +15,44 @@ The following are guidelines for contributing to the Edge AI Suites project, inc
 
 # Code of Conduct
 
-This project and everyone participating in it are governed by the [`CODE_OF_CONDUCT`](CODE_OF_CONDUCT.md) document. By participating, you are expected to adhere to this code.  
+This project and everyone participating in it are governed by the [`CODE_OF_CONDUCT`](CODE_OF_CONDUCT.md) document. By participating, you are expected to adhere to this code.
 
-# Security 
+# Security
 
-Read the [`Security Policy`](SECURITY.md).  
+Read the [`Security Policy`](SECURITY.md).
 
 # Get Started
 
-Clone the repository and follow the [`README`](README.md) to get started with the sample applications of interest.  
+Clone the repository and follow the [`README`](README.md) or
+[documentation's](https://docs.openedgeplatform.intel.com/) "Get Started" of the chosen
+applications.
 
 ```
     git clone https://github.com/open-edge-platform/edge-ai-suites.git
     cd edge-ai-suites
 ```
+Note that you do not need to clone the entire repository. You can clone just the portion you
+are interested with. To see how ti do it, check out the
+[Contributing to Open Edge Platform](https://docs.openedgeplatform.intel.com/canonical/OEP-articles/contribution-guide.html#repository-cloning-partial-cloning)
+article.
+
 
 # How to Contribute
 
 ## Contribute Code Changes
 
-> If you want to help improve Edge AI Suites, choose one of the issues reported in [`GitHub Issues`](https://github.com/open-edge-platform/edge-ai-suites/issues) and create a [`Pull Request`](https://github.com/open-edge-platform/edge-ai-suites/pulls) to address it.  
+> If you want to help improve Edge AI Suites, choose one of the issues reported in [`GitHub Issues`](https://github.com/open-edge-platform/edge-ai-suites/issues) and create a [`Pull Request`](https://github.com/open-edge-platform/edge-ai-suites/pulls) to address it.
 > Note: Please check that the change hasn't been implemented before you start working on it.
 
 ## Improve Documentation
 
 The easiest way to help with the `Developer Guide` and `User Guide` is to review it and provide feedback on the
-existing articles. Whether you notice a mistake, see the possibility of improving the text, or think more 
+existing articles. Whether you notice a mistake, see the possibility of improving the text, or think more
 information should be added, you can reach out to discuss the potential changes.
 
 ## Report Bugs
 
-If you encounter a bug, open an issue in [`Github Issues`](https://github.com/open-edge-platform/edge-ai-suites/issues). Provide the following information to help us 
+If you encounter a bug, open an issue in [`Github Issues`](https://github.com/open-edge-platform/edge-ai-suites/issues). Provide the following information to help us
 understand and resolve the issue quickly:
 
 - A clear and descriptive title
@@ -59,7 +66,7 @@ understand and resolve the issue quickly:
 
 Intel welcomes suggestions for new features and improvements. Follow these steps to make a suggestion:
 
-- Check if there's already a similar suggestion in [`Github Issues`](https://github.com/open-edge-platform/edge-ai-suites/issues).  
+- Check if there's already a similar suggestion in [`Github Issues`](https://github.com/open-edge-platform/edge-ai-suites/issues).
 - If not, open a new issue and provide the following information:
    - A clear and descriptive title
    - A detailed description of the enhancement
@@ -75,7 +82,7 @@ Before submitting a pull request, ensure you follow these guidelines:
 - Test your changes thoroughly.
 - Document your changes (in code, readme, etc.).
 - Submit your pull request, detailing the changes and linking to any relevant issues.
-- Wait for a review. Intel will review your pull request as soon as possible and provide you with feedback. 
+- Wait for a review. Intel will review your pull request as soon as possible and provide you with feedback.
 You can expect a merge once your changes are validated with automatic tests and approved by maintainers.
 
 # Development Guidelines
@@ -95,7 +102,7 @@ Clear and informative commit messages make it easier to understand the history o
 - Capitalize the first letter
 - Keep the message concise, ideally under 50 characters
 
-Please fill in the details as per the [pull request template](./.github/PULL_REQUEST_TEMPLATE.md) while submitting the 
+Please fill in the details as per the [pull request template](./.github/PULL_REQUEST_TEMPLATE.md) while submitting the
 pull request.
 
 ## Testing