ELS for Libraries: .NET applying new format#546
Open
sboldyreva wants to merge 8 commits into
Open
Conversation
ELSDOC-238: Migrate the .NET libraries page to the shared OS/Runtimes/Apps format with a single Installation section using ELSPrerequisites and ELSSteps split into Locate / Add credentials / Register repo / Install, plus a trailing dotnet restore tip. ELSDOC-242: Add CVE Tracker, Available fixes and Supported components links (filtered by ?product=.NET+Libraries) to the What's Next? footer alongside the existing VEX feed and Managing the ELS repository entries. https://claude.ai/code/session_01CAQhAZ8qmmMUbBL15E9gZe
…anaging-els-repository - Reorder Installation steps: Locate project (just find .csproj), Register repo, Add credentials, Install (restored detailed dotnet add package examples and dropped the .csproj XML tab). - Drop the standalone VEX section and the inline Package Source Mapping / Managing the TuxCare Source subsections — VEX feed is now only a card in What's Next, source management moves to the managing-els-repository page. - Extend managing-els-repository with a .NET tab under a new "Managing the TuxCare NuGet source" section: add/list/update/remove source, package source mapping, and upgrading installed packages as bullet points. - What's Next on the .NET libraries page now anchors to that .NET tab. https://claude.ai/code/session_01CAQhAZ8qmmMUbBL15E9gZe
…t's Next cards - Add a .NET tab to the existing #how-to-upgrade-to-a-newer-version TableTabs on the managing-els-repository page with the original Upgrading Packages content from the .NET libraries page (dotnet add package --version + dotnet build). - Drop the duplicated upgrade bullet from the new Managing the TuxCare NuGet source section; leave a cross-link to the upgrade section. - Split the .NET libraries page What's Next into two cards: a Managing NuGet sources card anchored to #managing-the-tuxcare-nuget-source and an Upgrading packages card anchored to the .NET upgrade tab. https://claude.ai/code/session_01CAQhAZ8qmmMUbBL15E9gZe
…nder Source code, fix CVE Tracker product - Vue template slot names cannot contain a dot, so '#.NET' was being parsed as the default slot and the tab + anchor broke. Switch the .NET slots to 'DotNet' / 'DotNetSources' and use the labels prop to display '.NET' in the dropdown. - Move the .NET NuGet source-management bullets into the existing Source code section as a second TableTabs tab alongside Java; drop the now redundant Managing the TuxCare NuGet source heading. - Update the .NET libraries page What's Next anchors to the new slot names and switch the CVE Tracker / Available fixes / Supported components links to ?product=.NET. https://claude.ai/code/session_01CAQhAZ8qmmMUbBL15E9gZe
Slot names and matching What's Next anchors are renamed from DotNet to dotnet and DotNetSources to dotnetSources. https://claude.ai/code/session_01CAQhAZ8qmmMUbBL15E9gZe
Match the dotnet/dotnetSources convention: Java -> java in the upgrade TableTabs and JavaSources -> javaSources in the source-code TableTabs, with labels prop preserving the 'Java' display text. https://claude.ai/code/session_01CAQhAZ8qmmMUbBL15E9gZe
Insert step 4 'Verify the source' in the .NET libraries Installation section that runs 'dotnet nuget list source'. The same command is kept as a bullet in the Managing the TuxCare NuGet source dropdown on the managing-els-repository page. https://claude.ai/code/session_01CAQhAZ8qmmMUbBL15E9gZe
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.