[Repo alignment] Write a common README for all docs projects and set it everywhere #36
Labels
No labels
Contributors' Guidance
Improve written Material
Contributors' Guidance
technical support measures
effort
high
effort
low
effort
medium
good first issue
help wanted
meeting topic
needs changes
needs reporter feedback
needs review
priority
high
priority
low
priority
medium
priority
on hold
type/content
type/misc
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
docs/tickets#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Subset of #18.
We need to come up with a shorter README for docs repos. The new README should:
And in order to close this issue, all repositories in the docs organization (except "service" repos like tickets) should use it. Published repositories outside the docs org should be left to do whatever they want, though we should let them know they might want to follow our lead.
Here's my suggestion for the common README. Let me know what do you think. ;)
I like it.
As it is for totally new people, I do not think they will know what 'including a local preview' means. So we could leave that out, and make sure the links are there from the Contributor Guide.
Good point. I'll remove it.
A couple more things @jonashub
If you don't mind, please edit it into the post above so I can copypaste it later and not worry about it :)
Here is a list of repos where I believe we should implement this:
Here I'm not completely sure:
Yeah, let's do the latter three as well.
E: Sorry, not the Contributor's Guide, that's the archived one and we have team-docs already covered.
Actually I'll just move that into the graveyard.
All right, looks like we're all done. Thanks @jonashub!