Target Docusaurus format #126
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I know that I should have opened an Issue first, but since I've found the following issues that are related and are non-answered, I tried to come up with something that would solve my problem.
I want to generate the Markdown files in a folder structure that makes sense on a Docusaurus docs website.
That means some conventions from Jekyll need to be overridden with different rules.
I've found 2:
On this PR I add a flag
type-folders
to address the second point.And I've built a new console project, that can be delivered as a dotnet tool, that plugs the Docusaurus file path rules into the generator.
Let me know if this is useful. It's solving my problem at the moment.
I'm happy to fine-tune it based on your feedback.