Replies: 1 comment
-
I have worked around my issue with the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
We have started using DocFx to generate Markdown files from our assemblies (using DLLs due to a mixture of F# and C#) which we publish on a GitBook site (using GitBook's SaaS approach).
I've been looking through past issues and discussions to figure out the best way to achieve what we are after, but haven't found anything definitive as of yet. Here are the requirements that we have due to the fact that we are using GitBook:
Acme.Plugins.Tasks.EndOfDayTask.md
) we want a nested structure for better readability (Acme/Plugins/Tasks/EndOfDayTask.md
)[Acme.Plugins.Tasks.EndOfDayTask](Acme/Plugins/Tasks/EndOfDayTask.md)
) and be relative to other pages ([Acme.Plugins.Tasks.EndOfDayTask](../Tasks/EndOfDayTask.md)
)xref
elements are not rendered at all on GitBook it seems, leading to confusing documentation for the readerSo far, I have put together a PowerShell script to handle 1 and 2, and I just need to solve the
xref
problem in 3. My script is getting quite complicated, making me rethink my process, which is currently:docfx metadata docfx.json
to create the flat file structure.
I appreciate that the Markdown output is intended as an intermediate step before
docfx build
, and is currently "beta". So I just wanted to get some opinions from the community on how I could do this better. Should I:docfx build
as Markdowndocfx
source with a newoutputFormat
ofmarkdownFinal
to try and meet my requirements earlier in the processAny guidance or feedback would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions