-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Github Readmes From Repos #12
Comments
You mean to import the README file of other repos as a new documentation inside DevDocs? I don't think this would be very useful because the file wouldn't be indexed/searchable and the documentation would have no icon. |
Maybe I am in the minority but this feature would be extremely useful for me. The majority of documentation I reference comes from smaller libraries hosted on github and npm. A few examples... https://github.com/component/dom I can do without an icon but most readmes are written in markdown which shouldn't be hard to parse and index. Even if importing the readme doesn't seem like the right solution some sort of ability for devdocs to import documentation from custom sources would be helpful. |
Ok. I agree the ability to import documentations automatically would be useful. I may give this a try in the future but for now my focus is on adding documentations manually. |
Closing this issue as I don't think it's feasible to import README files generically into DevDocs while keeping everything clean and organized. |
I would also very much like this feature. There is already a project that does this: Examples: The benefit is that the readability is improved and there could be a menu (generated from the headings). Maybe this can work like documentup, where you specify the target repository through the url, for example: |
@peteruithoven I like that idea, especially now that we have offline mode, but probably won't get to it in the near future. |
It would be really useful to be able to add a repo to devdocs and have it import that repos Readme or have some sort of similar plugin architecture.
The text was updated successfully, but these errors were encountered: