Conversation
Introduces _navbarLinks and _asfLinks configuration in docfx.json including the correct event page link. Adds a new navbar-links partial to render these links and updates the main navbar partial to include it.
Now the Api / Libraries works as intended, not splitting into two lines and the slash is restored.
Introduces _navbarLinks and _asfLinks configuration in docfx.global.json including the correct event page link. Adds a new navbar-links partial to render these links and updates the main navbar partial to include it.
- Added docfx.links.json to organize navigation and ASF links separately. It now includes the links. - Modified docfx.site.json to include docfx.links.json in globalMetadataFiles.
Added docfx.links.json to metadata and updated navbar links to point to the latest CI documentation. Enhanced docs.ps1 to automatically update both docfx.links.json with the current LuceneNetVersion during the build process, ensuring navigation and API links always reference the correct version.
…earing inside the apidocs. - Refactor navbar links to use individual properties and moved to the subsite.json. - docfx.links.json and navbar-links.tmpl.partial removed. - docs.ps1 restored as it was originally. - Removed the link json file reference from the metadata docfx.core.json.
…ka26/lucenenet into fix/apidocs-breadcrumb-toc-asf
- Change _navCliHref to absolute URL for published CLI docs - Removed the links jsons globalMetadataFiles leftover and the subsite one was added instead. - Auto-update CLI doc version in docs.ps1 - Improve navbar template indentation for readability and removed a debug message from it.
|
Hey @NightOwl888 , @paulirwin! First of all: Sorry this took so long. Some personal stuff came up and I should have communicated earlier. I did keep working on it on and I managed to invent a DocFX issue that did not need to exsist in the first place, and I spent too much time trying to fix it up until I found the actual cause and the current approach works now. The ASF links (and also the navigation links) are now in the docfx metadata. As for the apidocs, they are in the If you want a different structure where these links values are, just let me know and I will adjust it quickly! I just realized that the site was 'left behind' as I was troubleshooting the apidocs, and I will quickly make them more uniform by modify the site to match how the links are stored and called at the navbar partial. Then I will revert it from draft. |
…the apidocs - Replaced array-based navigation link config in docfx.json with individual metadata fields for each link. - Removed the navbar-links.tmpl.partial template as it become no longer necessary. - Updated navbar.tmpl.partial to render links directly from the new fields.
|
Now the site and apidocs are more uniform in how the navbar links are stored and rendered. Apologies about the delay again and thanks for your patience! |
1 participant
Render apidocs navbar links via DocFX metadata; fix breadcrumb; fix event link
Fixes #1215 (Continuation of #1198)
Description
api / {subsites}.