docs: update coc, contributing, readme

Author: pjsier

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at pjsier@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,19 @@
+# Contributing to `airtable-block-link-by-fields`
+
+Thanks for your interest in contributing! We follow the ["fork and pull"](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models) model where contributors create personal forks of this repository, commit changes on a new branch, and then open pull requests for their updates to be reviewed and merged.
+
+To get started, you can look for [issues labeled "help wanted"](https://github.com/pjsier/airtable-block-link-by-fields/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) and post a comment that you're interested as well as any questions you have about the issue. If the issue is available you'll be assigned, and from there you can create a pull request with your updates.
+
+All contributors are expected to follow our [code of conduct](./CODE_OF_CONDUCT.md).
+
+## Pull Requests
+
+GitHub has [documentation on creating pull requests](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/about-pull-requests) that explains the overall workflow. By default, new pull requests should be opened against the `main` branch of this repo.
+
+## Bug Reports
+
+Find something that isn't working the way it should? First, take a look through our [existing issues](https://github.com/pjsier/airtable-block-link-by-fields/issues) to see if someone has already reported it, and if not feel free to create a new issue. If you're not sure if your issue has already been raised, go ahead and make a new one, we'd rather get a duplicate than miss a bug.
+
+## Feature Requests
+
+Have an idea for a useful feature that isn't currently supported? Review our [open issues](https://github.com/pjsier/airtable-block-link-by-fields/issues) to see if it's already been mentioned, and if not you can create a new issue to discuss it.

README.md

@@ -2,7 +2,7 @@
 
 [![Build status](https://github.com/pjsier/airtable-block-link-by-fields/workflows/CI/badge.svg)](https://github.com/pjsier/airtable-block-link-by-fields/actions?query=workflow%3ACI)
 
-Airtable block for linking records by matching fields.
+Airtable block for linking records by matching fields. [Install in the Airtable marketplace](https://airtable.com/marketplace/blkQ7qqVJ3LgsfF0L/link-records-by-fields).
 
 Select a table to update, linked records to fill in, and what fields should match to link records in bulk. You can also configure the options for matching including whether it should be case-sensitive and if existing linked record fields should be overwritten.