Security Alerts: Delete old package-lock.json files

.github/ISSUE_TEMPLATE/BUG_REPORT.yaml

@@ -0,0 +1,69 @@
+name: Bug report 🐛
+description:
+  Something not working as expected? This is the place to report your issue.
+title: '[Bug]: '
+labels: 'type: bug 🐛'
+body:
+  - type: markdown
+    attributes:
+      value: '## Welcome!'
+  - type: markdown
+    attributes:
+      value: Thanks for taking the time to fill out this bug report.
+  - type: dropdown
+    id: package
+    attributes:
+      label: Package
+      description: Which package(s) are you using?
+      multiple: true
+      options:
+        - 'made-design-tokens'
+        - 'made-css'
+    validations:
+      required: true
+  - type: dropdown
+    id: browser
+    attributes:
+      label: Browser
+      description: Which browser(s) are you experiencing the issue?
+      multiple: true
+      options:
+        - Chrome
+        - Safari
+        - Firefox
+        - Edge
+  - type: input
+    id: version
+    attributes:
+      label: Package version
+      description: 'Which version(s) are you using?'
+      placeholder: e.g. v2.0.0
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: "Tell us more about the problem that you're running into"
+      placeholder: What did you see? What did you expect to see?
+    validations:
+      required: true
+    validations:
+      required: true
+  - type: input
+    id: example-url
+    attributes:
+      label: Reproduction/example
+      description: |
+        Please send us a code example for us to debug and investigate the issue
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description:
+        'How do we reproduce the error you described using the
+        reproduction/example link above?'
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/FEATURE_REQUEST_OR_ENHANCEMENT.yaml

@@ -0,0 +1,47 @@
+name: Feature request or enhancement 💡
+description: Suggest an idea for this project.
+title: '[Feature Request]: '
+labels: 'type: enhancement 💡'
+body:
+  - type: markdown
+    attributes:
+      value: '## Welcome!'
+  - type: markdown
+    attributes:
+      value:
+        Use this template if you want to request a new feature, or a change to
+        an existing feature. If you are reporting a bug or problem, please use
+        the bug template instead.
+  - type: textarea
+    id: problem
+    attributes:
+      label: The problem
+      description:
+        'Provide a clear and concise description of what the problem this new feature is trying to solve. (For example, I find it frustrating when...). Be sure to attach screenshots or videos to illustrate the problem.'
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: The solution
+      description: 'Provide a clear and concise description of what you would like to happen instead. Be sure to attach screenshots or videos to illustrate the solution if possible. Design specs are highly encouraged.'
+    validations:
+      required: true
+  - type: textarea
+    id: user-research
+    attributes:
+      label: Examples
+      description: Provide sample content, references, or audits of solutions solving the same problem in other applications/websites.
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Business priority
+      options:
+        - 'High Priority = pressing release'
+        - 'Medium Priority = upcoming release but is not pressing'
+        - 'Low Priority = release date is not dependent on fix or not upcoming'
+  - type: input
+    id: resources
+    attributes:
+      label: Available extra resources
+      description: 'What resources do you have to assist this effort?'

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

CONTRIBUTING.MD

@@ -1,19 +1,12 @@
 # Contribute to Made. for Developers
 
-Made is always evolving – thanks to you. 
-
-Every time you share bug fixes, components, or documentation with us, you’re helping us to understand your needs.
+Anyone, regardless of discipline, is encouraged to contribute to Made. We welcome everything from copy edits and bug fixes to new components.
 
 ## Propose an update or new feature
 
 Whether you’re proposing an update, a new feature or simply making something better, we welcome contribution. 
 
-Simply email an issue to <a href="mailto:[email protected]">[email protected]</a> and provide the following information:
-
-- A brief description of the update you want to propose.
-- Include mockups of any fidelity (optional)
-- Include any inspirations from other products (optional)
-- Once your request is raised, we’ll review and set up a meeting to discuss the proposal in greater detail.
+Simply open an issue for requesting a new feature by clicking on the  <a href="https://github.com/Mastercard/made/issues" target="_blank">Issues</a> tab above.
 
 We’ll cover the following:
 
@@ -22,15 +15,42 @@ We’ll cover the following:
 - Support needed to get the job done
 - Suitable timings that work for you
 - If your work meets our contribution criteria, your request will be added to our backlog and marked as 'To do'. 
-At this stage, you can either start contribution or leave it for a member of the Made production team to pick up.
 
+At this stage, you can either start contribution or leave it for a member of the Made production team to pick up.
 
 ## Submit an issue or bug fix
 
-To report bugs and leave feedback, open an issue on <a href="https://github.com/Mastercard/made/issues" target="_blank">GitHub</a> and provide the following information:
-
-- A brief description of the fix you want to propose.
-- What did you expect to happen? What happened instead? What would you like to see changed?
-- What browser are you working in?
-- Steps to reproduce the issue
-- Additional information (Screenshots or code)
+To report bugs and leave feedback, open an issue clicking on the  <a href="https://github.com/Mastercard/made/issues" target="_blank">Issues</a> tab above. and provide the following information:
+
+## Start contributing
+
+Please see contributing guide in each project for more information:
+
+- [Made Design Tokens](https://github.com/Mastercard/made/blob/develop/packages/made-design-tokens/CONTRIBUTING.md)
+- [Made CSS](https://github.com/Mastercard/made/blob/develop/packages/made-css/CONTRIBUTING.md)
+
+## What is the contribution process?
+1. **Issue:** Check repo for an _existing_ issue related to your contribution
+   first. If none exist, open a new issue. 
+2. **Development environment:** If you haven't already, fork and clone whichever
+   repo you want to contribute to. Then, create a new branch and add your
+   contribution in it.
+3. **Pull request:** Submit a PR. Be sure to fill out the template properly.
+4. **Approval:** Get PR approved by design and developers, or make any necessary
+   changes for approval. This process may be quick or take a few iterations of
+   feedback-update.
+5. **Documentation:** After design and dev have approved and merged PR, update
+   any website documentation if necessary. One of the best examples for this is
+   if you're contributing to component work which has website documentation
+   related to your contribution.
+
+Here are some contribution quick tips:
+
+- **Do** check repos for existing issues.
+- **Do** fill out the required template for contributions entirely; this
+  pertains to both issues and PRs.
+- **Do** follow existing coding and writing styles.
+- **Do** follow proper commit messages syntax.
+- **Do not** branch off another branch.
+- **Do not** include unrelated changes in the same PR.
+- **Do not** create one massive PR if it can be broken up into smaller PRs.

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+Closes #
+
+{{short description}}
+
+#### Changelog
+
+**New**
+
+- {{new thing}}
+
+**Changed**
+
+- {{change thing}}
+
+**Removed**
+
+- {{removed thing}}
+
+#### Testing / Reviewing
+
+{{ Add descriptions, steps or a checklist for how reviewers can verify this PR works or not }}