-
Notifications
You must be signed in to change notification settings - Fork 152
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
Meta: Where shall certain resources live? #445
Comments
More to the point, I'm afraid that just creating them as .md files in this repo will hurt their discoverability. |
@jorydotcom do you have suggestions of where they would be better discoverable? I agree that as the content grows some structure will help. Did you have something in mind like a sub-directory called "Foundation Services" or a repo with a similar name? |
How about a repo called "foundation"? It's a convention used in other projects, and opens the opportunity to set up an issue tracker for Foundation-specific tasks. |
Hmmm. @brianwarner I feel like that might not be the obvious place for a new project / community member to look - I don't know that I would think to look under 'Foundation'. I feel like I want something like 'Project Resources' or 'Project Benefits' or something? |
My thinking is in line with @jorydotcom I think we need a name that will make people think its a list of resources/benefits that they can access. |
We have some documentation that's been created for projects such as:
And I imagine as we onboard more projects and help them get started, we will want to create other similar guides that help projects get familiar with what we can do to help. Where shall documents like this live long-term?
The text was updated successfully, but these errors were encountered: