tiptap/docs/overview/contributing.md
Philipp Kühn 569aa15c4f Merge branch 'main' of https://github.com/ueberdosis/tiptap into docs/remove-gridsome
# Conflicts:
#	docs/experiments/collaboration-annotation.md
#	docs/experiments/global-drag-handle.md
2021-09-17 23:45:04 +02:00

1.9 KiB
Raw Blame History

tableOfContents
true

Contributing

Introduction

tiptap would be nothing without its lively community. Contributions have always been and will always be welcome. Here is a little bit you should know, before you send your contribution:

Welcome examples

  • Failing regression tests as bug reports
  • Documentation improvements, e. g. fix a typo, add a section
  • New features for existing extensions, e. g. a new configureable option
  • New extensions, which dont require changes to the core or other core extensions
  • Well explained, non-breaking changes to the core

Submit ideas

Make sure to open an issue and outline your idea first. Well get back to you quickly and let you know if there is a chance we can merge your contribution.

Set up the development environment

Its not too hard to tinker around with the official repository. Youll need Git, Node and Yarn installed. Here is what you need to do then:

  1. Copy the code to your local machine: $ git clone git@github.com:ueberdosis/tiptap.git
  2. Install dependencies: $ yarn install
  3. Start the development environment: $ yarn start
  4. Open http://localhost:3000 in your favorite browser.
  5. Start playing around!

Our code style

There is an eslint config that ensures a consistent code style. To check for errors, run $ yarn run lint. Thatll be checked when you send a pull request, too. Make sure its passing, before sending a pull request.

Testing for errors

Your pull request will automatically execute all our existing tests. Make sure that they all pass, before sending a pull request. Run all tests locally with $ yarn run test or run single tests (e. g. when writing new ones) with $ yarn run test:open.

Futher questions

Any further questions? Create a new issue or discussion in the repository. Well get back to you.