<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=551776) </details> <!--IssueSummary end--> ## Problem The current devfile interface displays file system paths instead of meaningful names, creating confusion for users trying to identify and select the correct devfile configuration. For example: | | | ------ | |  | ## Proposed Solution Display the human-readable [`metadata.name` and/or `metadata.displayName`](https://devfile.io/docs/2.2.0/create-devfiles) field from the devfile instead of the file path. The file path can be shown as supplementary hover information for users who need that technical detail. This change would: - Enable users to quickly identify the correct devfile by its descriptive name - Reduce configuration errors and support requests - Improve onboarding experience for new developers - Maintain technical information accessibility without cluttering the interface For example: | | | ------ | |  | ## Business Impact - **Reduced Developer Productivity**: Users waste time deciphering cryptic file paths to find the right devfile, slowing down development workflows - **Increased Support Burden**: Unclear naming leads to more support tickets and questions from confused users - **Higher Error Rate**: Users may select incorrect devfiles due to poor identification, causing failed deployments or misconfigurations - **Poor User Experience**: Technical file paths create a barrier for less technical users and new team members, impacting adoption rates