-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Hi! Neat project!
Two questions:
- Do you discourage usage of
.design/DESIGN.md
(or.design/README.md
) when following the "minimal" guidelines? Just curious, the first project I looked at (from the collection at https://contribute.design/projects) is using.design/DESIGN.md
. - Do you discourage usage of a root
DESIGN.md
(in place of.design/README.md
, with other files remaining nested in.design
) when following the "Extended" or "Full Fledged" guidelines? This pattern seems more "discoverable" for designers who may be unaware of contribute.design, and are encountering an open source project organically.
One suggestion: a lot of projects use a root CONTRIBUTING.md
to bring new contributors up to speed / document best practices for contributors. Guessing most implementors (of your guidelines) will think of this, but maybe this repo should suggest adding a link from CONTRIBUTING.md
to DESIGN.md
(or .design/README.md
).
Metadata
Metadata
Assignees
Labels
No labels