diff --git a/README.md b/README.md index 4e7795159b1bf98f09b6e0e1eed97fe83a4a26c1..b5fe70be62df791795ef0f68bcc189a4d8b11697 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,9 @@ For a more detailed walkthrough, check out our [Getting Started](docs/getting-st # Contributing -To get started with a development installation of the Query Server and learn more about contributing, please follow the instructions at our [Developers Guide](docs/developers-guide.md). +To get started with a development installation of the Metabase, follow the instructions at our [Developers Guide](docs/developers-guide.md). + +The take a look at our [Contribution Guide](docs/contributing.md) for information about our process and where you can fit in! # Extending and Deep Integrations diff --git a/docs/contributing.md b/docs/contributing.md index e02261a70f638b58f79fb95c813728b5cd3a0669..27bbedf56375d9edebe4e5e37d2f9be42bfda6a5 100644 --- a/docs/contributing.md +++ b/docs/contributing.md @@ -25,13 +25,13 @@ We actively look for new feature ideas from our community, user base and our own We typically will collect a group of issues or suggestions into a new topline feature concept. Typically we'll create a working document that collects all "Open Questions" regarding to what the feature is meant to do, and more importantly not do. We'll chat with our users, maybe do in depth interviews and generally try to tightly define the feature. -### C) Sic a product designer on a feature +### C) Design the feature Once a feature has been defined, typically it will be taken on by a product designer. Here, they will produce low fi mocks, get feedback from our users and community, and iterate. Once the main UX flows have been dialed in, there will be a hi-fidelity visual design. -### D) Hand off the hi-fi visual design to an engineer +### D) Hand off the design to an engineer This design is then handed off to one or more engineers. Together with the designer who owns the feature, they will work on the feature via a Pull Request.