add code of conduct and contributing.md

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

README.md

@@ -27,8 +27,8 @@ The philosophy is that the main thread should be dedicated to your code, and any
 
 - [@QwikDev](https://twitter.com/QwikDev)
 - [@Builderio](https://twitter.com/builderio)
-- [Local Development](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#local-development)
-- [For Plugin Authors / Developers](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#plugin-authors-developers)
+- [Local Development](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#local-development)
+- [For Plugin Authors / Developers](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#plugin-authors-developers)
 
 ## Related Projects
 
@@ -46,4 +46,3 @@ The philosophy is that the main thread should be dedicated to your code, and any
        </picture>
    </a>
 </p>
-

docs/_table-of-contents.md

@@ -38,7 +38,7 @@
   - [End-to-end Tests](/tests/)
   - [Services](/tests/benchmarks/services/)
   - [Benchmark](/tests/benchmarks/)
-  - [Local Development](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md)
+  - [Local Development](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md)
   - [Github](https://github.com/BuilderIO/partytown)
   - [@QwikDev](https://twitter.com/QwikDev)
   - [@Builderio](https://twitter.com/builderio)

docs/common-services.md

@@ -14,11 +14,11 @@ Below is a list of plugins / libraries that are tested & known to be working wit
 | [Hubspot Tracking](https://developers.hubspot.com/docs/api/events/tracking-code)              | "\_hsq.push"                                                                  |                                                     |
 | [Intercom](https://developers.intercom.com/installing-intercom/docs/intercom-javascript)      | "Intercom"                                                                    |                                                     |
 | [Klaviyo](https://developers.klaviyo.com/en/docs/javascript-api)                              | "\_learnq.push"                                                               | "static.klaviyo.com", "static-tracking.klaviyo.com" |
-| [TikTok Pixel](https://ads.tiktok.com/marketing_api/docs?rid=959icq5stjr&id=1701890973258754) | "ttq.track", "ttq.page", "ttq.load" 
-| [Mixpanel](https://developer.mixpanel.com/docs/javascript-quickstart) | "mixpanel.track" |                                                     |
+| [TikTok Pixel](https://ads.tiktok.com/marketing_api/docs?rid=959icq5stjr&id=1701890973258754) | "ttq.track", "ttq.page", "ttq.load"                                           |
+| [Mixpanel](https://developer.mixpanel.com/docs/javascript-quickstart)                         | "mixpanel.track"                                                              |                                                     |
 
 If you would like to add to this list,
 
-- Refer to the ["for Plugin Authors / Developers"](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#plugin-authors--developers) section to see how you can validate whether a library / plugin works with Partytown.
+- Refer to the ["for Plugin Authors / Developers"](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#plugin-authors--developers) section to see how you can validate whether a library / plugin works with Partytown.
 - Send us a PR so that we can have a scenario checked in that validates it.
 - Please [edit this doc](https://github.com/BuilderIO/partytown/edit/main/docs/common-services.md) to add your plugin / library and its configuration so that others can start using it!

docs/faq.md

@@ -17,7 +17,7 @@ Please first search through the [Github issues](https://github.com/BuilderIO/par
 If a similar [issue](https://github.com/BuilderIO/partytown/issues) does not already exist, please [open an issue](https://github.com/BuilderIO/partytown/issues/new/choose) that includes:
 
 - Minimal Reproduction Case: If maintainers and contributors are unable to reproduce the same error, then it makes it very difficult to debug and fix. Any issued opened without a minimal reproduction example will be closed.
-- E2E Test: A good example of an End-to-end test is one where the test fails before the fix, and passes after the fix. But also, all the other tests pass too. Please see [Submitting Issues And Writing Tests](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#submitting-issues-and-writing-tests) for more details.
+- E2E Test: A good example of an End-to-end test is one where the test fails before the fix, and passes after the fix. But also, all the other tests pass too. Please see [Submitting Issues And Writing Tests](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#submitting-issues-and-writing-tests) for more details.
 
 ## Why do some scripts work, and others don't with Partytown?
 
@@ -27,8 +27,8 @@ Most of yesterday's and today's third-party scripts were built from the ground-u
 
 Unfortunately, the project contributors and maintainers don’t have the capacity to debug every single third-party script on external websites. As an Open-Source project, Partytown's goal is to help encourage the community to assist one another. Helping to improvement the project can come in many forms:
 
-- [Opening issues](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#submitting-issues-and-writing-tests) with minimal reproduction cases
-- Creating fixes with [Pull Requests](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#submitting-issues-and-writing-tests)
+- [Opening issues](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#submitting-issues-and-writing-tests) with minimal reproduction cases
+- Creating fixes with [Pull Requests](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#submitting-issues-and-writing-tests)
 - Adding [End-to-end tests](/tests/)
 
 Additionally, Github issues is a place to explain a problem in detail, along with a reproduction case for maintainers. However, Github issues is not the best place to ask how-to questions since project contributors and maintainers don’t have the capacity to debug external websites and the many third-party scripts. Any issues opened asking that are not following these guidelines will be closed.
@@ -37,4 +37,4 @@ Additionally, Github issues is a place to explain a problem in detail, along wit
 
 Many sites are already successfully using Partytown in production. However, what's most important is testing your scripts first, as what works for one website using a certain third-party script, may not work for your site using a different script. If your scripts work in production that’s great, they shouldn't suddenly stop working (no different that a traditional third-party script).
 
-However, if you're struggling with a certain scenario, please see the [Submitting Issues And Writing Tests](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#submitting-issues-and-writing-tests).
+However, if you're struggling with a certain scenario, please see the [Submitting Issues And Writing Tests](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#submitting-issues-and-writing-tests).

docs/index.md

@@ -64,7 +64,7 @@ Below are just a few examples of third-party scripts that might be a good candid
 
 We try and keep a list of all the plugins and libraries that we know of that works out-of-the-box in Partytown, but we would love your help as plugin & library authors and contributors to keep this list growing.
 
-We have [some documentation](https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#plugin-authors--developers) on how you could create and check-in an integration test that shows how your library / plugin works on Partytown. And if it works, then we would love to have the configuration needed (if any) on our [Common Services page](/common-services)
+We have [some documentation](https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#plugin-authors--developers) on how you could create and check-in an integration test that shows how your library / plugin works on Partytown. And if it works, then we would love to have the configuration needed (if any) on our [Common Services page](/common-services)
 
 ## Articles
 

tests/index.html

@@ -66,12 +66,12 @@ <h1>Partytown Tests 🎉</h1>
     </p>
     <p>
       Please see the
-      <a href="https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#local-development"
+      <a href="https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#local-development"
         >local development</a
       >
       page for more information on how to re-create issues locally,
       <a
-        href="https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#submitting-issues-and-writing-tests"
+        href="https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#submitting-issues-and-writing-tests"
         >submit issues and writing tests</a
       >. Being able to recreate the issue with a minimal amount of code makes it easier debug.
     </p>
@@ -149,19 +149,19 @@ <h2>More Info</h2>
       <li><a href="https://partytown.builder.io/">Documentation</a></li>
       <li><a href="https://github.com/BuilderIO/partytown/tree/main/tests">E2E Tests</a></li>
       <li>
-        <a href="https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#local-development"
+        <a href="https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#local-development"
           >Local Development</a
         >
       </li>
       <li>
         <a
-          href="https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#submitting-issues-and-writing-tests"
+          href="https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#submitting-issues-and-writing-tests"
           >Submitting Issues And Writing Tests</a
         >
       </li>
       <li>
         <a
-          href="https://github.com/BuilderIO/partytown/blob/main/DEVELOPER.md#plugin-authors--developers"
+          href="https://github.com/BuilderIO/partytown/blob/main/CONTRIBUTING.md#plugin-authors--developers"
           >Plugin Authors / Developers</a
         >
       </li>