paulirwin commented on issue #793:
URL: https://github.com/apache/lucenenet/issues/793#issuecomment-2349070692

   @Shazwazza Thanks, I'd appreciate any assistance! It indeed does not support 
the old plugins, but those just replace markdown elements with things like 
environment variables, so I'm punting on that for now and saving that for the 
end. So currently I'm just trying to get the docs to build correctly without 
plugins enabled, and that's causing issues. It's complaining about a duplicate 
toc.yml file, which Shad told me you were able to work around previously. I 
think this is a large part of why the individual docfx json files (scripted via 
docs.ps1) fail to generate correct output for the individual library "sites." 
You can check out my progress here so you don't have to start from the 
beginning: https://github.com/paulirwin/lucene.net/tree/issue/911 - I've 
improved the docs.ps1 script to install the latest verison of docfx as a global 
tool, fixed a lot of doc build warnings, etc.
   
   Running the docfx global tool manually on the combined file generates a site 
that mostly works (again without plugins yet, so env vars don't work), but if 
you clean your repo and run docs.ps1 you'll see that the site is broken for all 
of the libraries off the main site.


-- 
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: dev-unsubscr...@lucenenet.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to