-
Notifications
You must be signed in to change notification settings - Fork 708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate pages corresponding to Markdown files in directories #1870
Comments
This is something I'd like to include in TypeDoc itself, but will probably be a part of the guides work that's planned for 0.24, probably won't happen for a while... |
Another, maybe simpler way, would be to just list a docs files with their path and create static docs from it, in a separate menu. Just to wrap existing docs into code-generated one. |
I see the Guides project board is now closed - do there happen to be plans for this idea now? |
I believe I closed it since GitHub started redirecting "old" projects to the new projects, and haven't gotten around to creating a new one since I've been meaning to finish 0.24 first, which won't include it. Have been busy with other things recently... |
I would go one step further and say that generally all md files should be taken into account. Suggested SolutionSimilar to what Compodoc does, it would be extremely helpful if typedoc would consider md (Markdown) files that are in the same directory as the class and have the same filename. These MD files could be displayed in a tab from the displayed class or linked quite high up in the document. Example
|
Another vote for this. We have a monorepo-like structure with components living in their own directories, with their own READMEs. It would be nice if those READMEs were also picked up by typedoc. |
Fixed with TypeDoc 0.26, which is releasing 2024/06/21 |
TypeDoc currently includes the content of
README.md
in the generatedindex.html
. It would be useful ifREADME.md
s in subdirectories also caused corresponding pages to be generated. Doing so would add a way for directories themselves to be documented, creating a place to discuss project organization or other things that apply to more than a single file, as well as a place to document non-TypeScript files.This should probably be labelled enhancement and plugin idea.
The text was updated successfully, but these errors were encountered: