NightOwl888 commented on issue #1215: URL: https://github.com/apache/lucenenet/issues/1215#issuecomment-3497652773
@zka26 - I don't have much of a preference as to where the links are in the HTML, but docfx might. I asked ChatGPT how this might work within the docfx build and it suggested adding a new template file: https://chatgpt.com/share/690cb2a4-42c8-8005-ba83-0b40773f29a7 I don't recall the exact reason, but we are using full URL paths in the final output (at least for some links). This means that when building locally, the paths are different than when we deploy the site live. With that in mind, I like option 3 for putting the links in the configuration where docfx can process them (or our scripts can pre-process them) when building the site. Ideally, this would all happen through docfx, but it has historically been hard to figure out how to make it work right at times and we eventually just give up and use Powershell to patch any behavior we cannot make work. We really should fix the navbars so other crawlers can index them, as well. Ideally we would ensure the entire navbar is output as HTML when docfx does a build, not just the ASF links. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
