feat(docs): add extension collections overview and integrate into getting started flow#950
feat(docs): add extension collections overview and integrate into getting started flow#950PratikWayase wants to merge 4 commits intomicrosoft:mainfrom
Conversation
katriendg
left a comment
There was a problem hiding this comment.
Thanks for putting this together, @PratikWayase! The collections overview page and cross-linking are a solid start. I have a few items to address before we can merge.
Unrelated changes — please remove
This PR includes a file that aren't part of #859 and should be submitted separately:
.github/workflows/weekly-security-maintenance.yml — Adding stale SHA issue auto-creation (64 new lines) is a workflow/security change with no connection to #859. This needs its own PR with appropriate review.
Missing items from the acceptance criteria in #859
The issue specifies several requirements that aren't addressed yet:
- Expandable or linked descriptions per collection — The table is a good start, but #859 asks for each collection to have an expandable description (or link) showing the specific agents and capabilities included. Currently it's just a flat table row.
- Maturity status indicators — Design Thinking should be marked Preview and Experimental should be marked Experimental, per the implementation notes in the issue.
- Homepage hero section CTA — The issue proposes an update to
docs/docusaurus/src/pages/index.tsxfor a hero section install CTA. This file wasn't touched. - Hub card destination — The new hub card links directly to the marketplace, but the issue asks for a link to the collections overview page (or both marketplace and collections overview), so users can compare bundles before installing.
Code quality items
VsCodeExtensionIconformatting — The component has inconsistent quote styles (single vs double), irregular indentation, and spacing that doesn't match the existing icon components in the file. Please align with the style ofDesignThinkingIconand others already inIcons/index.tsx.- SVG gradient bug —
offset="100"on the last gradient stop should beoffset="100%". collections.mdfrontmatter — Theauthorfield uses lowercasepratik wayase; please use proper casing.- Missing trailing newline —
collections.mdis missing a final newline. - Hardcoded artifact counts — The issue notes that counts should be verified against
collections/*.collection.yml. Please double-check these are accurate as of the currentmainbranch.
Summary
Please:
- Remove the two unrelated file changes and submit them as separate PRs
- Address the missing acceptance criteria items listed above
- Fix the code quality items
Happy to re-review once these are addressed!
|
Thanks for the detailed review, @katriendg! So far, I’ve focused on improving the collections overview page. I’ve added expandable sections to better surface the agents and capabilities within each collection. I also noticed that only the hve-core marketplace link is working. The other collection links (e.g., ADO, etc.) are returning 404 errors when using URLs like: Could you confirm whether these extensions are not published yet, or if I should be using a different naming convention for the marketplace links? The remaining items (maturity indicators, homepage CTA, hub card updates, and code quality fixes) are still pending I’ll address those next. Also noted on the unrelated workflow file I’ll remove it and raise a separate PR for that. Please let me know if the current approach for the collections page looks good and how I should handle the marketplace links.
|
|
Thanks @PratikWayase, I believe your expandable collections look nicely! For the extensions, maybe we have a broken link somewhere, but all current collections are available and published: So the link for ADO should be https://marketplace.visualstudio.com/items?itemName=ise-hve-essentials.hve-ado, we may have had a rename at some point. The latter is the working and correct link. |


Pull Request
Description
This PR improves the extension installation experience by introducing a collections overview page and integrating it into the Getting Started documentation flow.
The goal is to help users quickly understand available HVE extension bundles and choose the appropriate workflow.
Changes Included
Related Issue(s)
Closes #859
Type of Change
Code & Documentation
Testing
The documentation changes were validated by:
Commands Executed
Checklist
Required Checks
Required Automated Checks
npm run lint:mdnpm run spell-checknpm run lint:frontmatternpm run validate:skillsnpm run lint:md-linksnpm run lint:psnpm run plugin:generate(not applicable)Security Considerations
Additional Notes
This change focuses on improving discoverability of extension collections and integrating them into the installation and Getting Started workflow, supporting the simplified extension install experience described in Issue #859.