You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been recently evaluating Quarto for migrating a docsify doc to quarto. To give you some context, we have a page (doc.flux.audio), that host all our product documentation and it's generated from one GitHub repository.
So, I've started to look at how I could structured this with quarto. Apparently, each product documentation could be one book, which provide both html and pdf output : great!
But we also need some kind of landing page that redirect to the different books. This were I struggle to find the most elegant way to do this. I've tried to have books project inside a website project, but I quickly understand that it is not supported by quarto. Another solution I've tried is to have a website project that build its navbar from the html files generated by the other books project. It works, but it makes the whole doc a bit more tedious to build. I've also tried the new feature in Quarto 1.3 that allows to have an alternate render, but as we have several several markdown files per product documentation, it generate multiple pdf which is not ideal.
I've red through most of the quarto documentation, including profiles and variables, but at this point, I haven't seen how it could help me.
Do you have any advices on how to handle this use case the best ? Thank you !
staleIssues open for 30+ days without providing a "working" reproducible example
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there,
I've been recently evaluating Quarto for migrating a docsify doc to quarto. To give you some context, we have a page (doc.flux.audio), that host all our product documentation and it's generated from one GitHub repository.
So, I've started to look at how I could structured this with quarto. Apparently, each product documentation could be one book, which provide both html and pdf output : great!
But we also need some kind of landing page that redirect to the different books. This were I struggle to find the most elegant way to do this. I've tried to have books project inside a website project, but I quickly understand that it is not supported by quarto. Another solution I've tried is to have a website project that build its navbar from the html files generated by the other books project. It works, but it makes the whole doc a bit more tedious to build. I've also tried the new feature in Quarto 1.3 that allows to have an alternate render, but as we have several several markdown files per product documentation, it generate multiple pdf which is not ideal.
I've red through most of the quarto documentation, including profiles and variables, but at this point, I haven't seen how it could help me.
Do you have any advices on how to handle this use case the best ? Thank you !
Beta Was this translation helpful? Give feedback.
All reactions