-
Notifications
You must be signed in to change notification settings - Fork 910
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
Should we remove the docs/
folder from the template?
#2381
Comments
My kneejerk response is that @astrojuanlu and I just revised the section in the tutorial about building docs, and we'd have to rewrite it 😆 I'd also argue that it subtly "reminds" project owners to create documentation as part of best-practice. But, in truth, it's not much effort to do the rewrite, and I'm not convinced that reminder is particularly beneficial. We were planning to remove the contents of docs ( For that reason, and for simplicity, I say +1 to let's take it out. TL;DRAdvantages of retaining
|
As @stichbury said, rewriting that guide is not an issue at all. I'm on the fence about this. Generally speaking about gh-2149, maybe we could have a more interactive workflow that lets users pick what parts of the default template they want. That discussion should happen there however. About just retaining the |
Closing this in favour of the utility add-ons work:#2388 |
Description
Sub-task of #2149
The text was updated successfully, but these errors were encountered: