Skip to content
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

[FEATURE] - add override flag for default location of README.md, CHANGELOG.md, CONTRIBUTING.md, LICENSE.md, TODO.md files #857

Closed
greenstevester opened this issue Oct 24, 2019 · 7 comments

Comments

@greenstevester
Copy link

Overview of the feature

add a flag to specify/override the default location of README.md, CHANGELOG.md, CONTRIBUTING.md, LICENSE.md, TODO.md files?

Motivation for or Use Case

I would like to override the default location and have them reside in a ./docs/folder instead of the project root

Related issues

None - it's a new feature

@dopry
Copy link

dopry commented Dec 11, 2019

I'd like to add a second use case. We're developing an angular component library. We have structure as follows /projects/lib, projects/docs, /projects/showcase. The /README.md is written for the developers of the component library so we can easily onboard developers to working on the component library and it is the first documentation they see when visiting the repo. /projects/lib/README.md is written for the consumers of our component library and has quick starts instructions and links to references. It is published with our packages. Compodoc also targets our component library consumers. We would like it to include the /projects/lib/README.md. It is currently pulling in the README.md written for our component library developers. Changing the way the repo is organized would create and awkward developer experience for our internal developers, and as it stands it creates and awkward developer experience for our consumers. Being able to specify an Alternate README.md would allow us to deliver a better DX to both of our developer audiences.

@greenstevester
Copy link
Author

Verbatim to @dopry 's usage of compodoc, we also are developing an angular component library which has two audiences, 1) internal component library developers and 2) consumers of the library.
If compodoc was extended to cover this use-case, I am sure it would gain a substantial user-base as I already investigated using dgeni, storybook, gitbook, angulardoc.io,readTheDocs and all of them fell short of what we needed.

@stale
Copy link

stale bot commented Feb 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 15, 2020
@dopry
Copy link

dopry commented Feb 15, 2020

@vogloblinsky hey what's will stalebot shooting down feature requests?

@stale stale bot removed the wontfix label Feb 15, 2020
@stale
Copy link

stale bot commented Apr 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Apr 15, 2020
@stale
Copy link

stale bot commented Apr 22, 2020

This issue has been automatically closed because it has not had recent activity. Please file a new issue if you are encountering a similar or related problem. Thank you for your contributions.

@stale stale bot closed this as completed Apr 22, 2020
@lock
Copy link

lock bot commented Jun 24, 2020

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants