Reviewing files that changed from the base of the PR and between e04d727 and cf7cef5.

• examples/sites/src/views/components-doc/cmp-config.js (1 hunks)
• examples/sites/src/views/components-doc/index.vue (1 hunks)
• examples/sites/src/views/components-doc/plus.vue (1 hunks)
• examples/sites/vite.extend.ts (1 hunks)

examples/sites/src/views/components-doc/cmp-config.js (1)

27-27: Added 'grid-kit' to the exclusion list

The getWebdocPath function has been updated to exclude 'grid-kit' from being mapped to 'grid', following the same pattern as the existing exclusion for 'grid-select'. This ensures that 'grid-kit' components have their own documentation path rather than being redirected to the generic 'grid' path.

examples/sites/src/views/components-doc/index.vue (1)

9-9: Fixed the Plus component import path

The import statement has been corrected to import the Plus component from './plus.vue' instead of './pc.vue', ensuring that the correct component is used when the application is in 'plus' mode.

examples/sites/vite.extend.ts (1)

82-82: Updated demos path to use the root plusdocs directory

The demosPath variable has been modified to point to '../plusdocs' instead of '../plusdocs/pc', reflecting a change in the directory structure for plus mode documentation files.

examples/sites/src/views/components-doc/plus.vue (2)

19-27: Improved conditional loading of demo configuration files

The conditional logic for loading demo configuration files has been refactored to be more explicit. Now, the code clearly pushes the import for demo configuration only when the component ID is not in the excluded list ('interfaces', 'types', 'classes'). This change makes the code more readable and maintainable.

---

12-12:

❓ Verification inconclusive

Simplified markdown file path construction

The path construction for loading markdown documentation has been streamlined by directly using the component ID in the path instead of passing it through the getWebdocPath function. This simplification should make path resolution more intuitive.

---

🏁 Script executed:

#!/bin/bash
# Check if any components might still require the getWebdocPath function for special path handling
cd examples/sites
# First, get a list of components that use special path handling in getWebdocPath
components=$(grep -A 7 "getWebdocPath" src/views/components-doc/cmp-config.js | grep "return" | grep -v "path" | sed 's/.*return //' | sed "s/'//g" | sed 's/"//g' | sed 's/ //g' | tr -d '\n')
echo "Components with special path handling: $components"

# Then check if any markdown files follow these special path patterns
echo "Checking for markdown files using special paths..."
find ../plusdocs/app -name "*.md" | grep -E "$components"

Length of output: 592

---

Simplified Markdown File Path Construction – Please Verify Directory Structure

The update to examples/sites/src/views/components-doc/plus.vue now directly builds the markdown file path using the component ID instead of the legacy getWebdocPath function, which streamlines path resolution. Note that our verification script did identify a special case (gridchartdirectives), but attempting to locate markdown files using the old special path logic resulted in a missing directory (plusdocs/app). Please manually verify that this structural change hasn’t affected any components that might still rely on the previous special path handling.

• Confirm that components requiring special handling (e.g., gridchartdirectives) are unaffected.
• Verify that markdown documentation is present at the intended location and that no legacy paths are inadvertently needed.