Update README.md

[starbelly]

The README.md does not currently reflect the following:

• contributing
• generating events
• generating news letters

[paulo-ferraz-oliveira]

How's this for "contributing"? (I can pull request and tweak, if accepted)

(shamelessly adapted from https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)

Contributing to erlef/website

We want to make contributing to this project as easy and transparent as possible.

Our Development Process

We use GitHub to sync code to and from our internal repository. We'll use GitHub to track issues and feature requests, as well as accept pull requests.

Pull Requests

We actively welcome your pull requests.

1. Fork the repo and create your branch from develop.
2. If you've added code that should be tested, add tests. (if in doubt, ask)
3. If you've changed APIs, update the documentation.
4. Ensure the test suite passes.
5. Make sure your code lints.
6. When contributing be sure to accept our required acknowledgement of non-favouritism.

Issues

We use GitHub issues to track public bugs and feature requests. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue, or describe the intended feature.

License

By contributing to erlef/website, you agree that your contributions will be licensed under its Apache License Version 2.0.

[starbelly]

I like it! I'm thinking we should switch to main from develop though, thoughts? Also we don't have an internal repository.

[paulo-ferraz-oliveira]

I'm not opposed to that change, though I like semantics where appropriate. Production is effectively the deployed stuff, right? So probably develop should become staging?

[starbelly]

I think main can implicitly mean this should go on staging before production, but I'm not strongly tied to that idea either. I think I just like main because it's short :p It's also becoming a standard.

[paulo-ferraz-oliveira]

I'm OK with either. 😄