# Contributing: Overview and Orientation
Love Redwood and want to get involved? You’re in the right place and in good company! As of this writing, there are more than 250 contributors who have helped make Redwood awesome by contributing code and documentation. This doesn't include all those who participate in the vibrant, helpful, and encouraging Forums and Discord, which are both great places to get started if you have any questions.
There are several ways you can contribute to Redwood:
- join the community Forums and Discord server — encourage and help others 🙌
- triage issues on the repo and review PRs 🩺
- write and edit docs ✍️
- and of course, write code! 👩💻
Before interacting with the Redwood community, please read and understand our Code of Conduct.
⚡️ Quick Links
There are several contributing docs and references, each covering specific topics:
- 🧭 Overview and Orientation (👈 you are here)
- 📓 Reference: Contributing to the Framework Packages
- 🪜 Step-by-step Walkthrough (including Video Recording)
- 📈 Current Project Status: v1 Release Board
- 🤔 What should I work on?
# The Characteristics of a Contributor
More than committing code, contributing is about human collaboration and relationship. Our community mantra is “By helping each other be successful with Redwood, we make the Redwood project successful.” We have a specific vision for the effect this project and community will have on you — it should give you superpowers to build+create, progress in skills, and help advance your career.
So who do you need to become to achieve this? Specifically, what characteristics, skills, and capabilities will you need to cultivate through practice? Here are our suggestions:
All of these are applicable in relation to both others and yourself. The goal of putting them into practice is to create trust that will be a catalyst for risk-taking (another word to describe this process is “learning”!). These are the ingredients necessary for productive, positive collaboration.
And you thought all this was just about opening a PR 🤣 Yes, it’s a super rewarding experience. But that’s just the beginning!
# What should I work on?
Even if you know the mechanics, it’s hard to get started without a starting place. Our best advice is this — dive into the Redwood Tutorial, read the docs, and build your own experiment with Redwood. Along the way, you’ll find typos, out-of-date (or missing) documentation, code that could work better, or even opportunities for improving and adding features. You’ll be engaging in the Forums and Chat and developing a feel for priorities and needs. This way, you’ll naturally follow your own interests and sooner than later intersect “things you’re interested in” + “ways to help improve Redwood”.
There are other more direct ways to get started as well, which are outlined below.
# Roadmap to Redwood v1: Project Boards and GitHub Issues
Over the next few months, our focus is to achieve a v1.0.0 release of Redwood. You can read Tom’s important announcement about the v1 release candidate process via this forum post.
What a v1 release candidate means:
- all core features are complete and
- we are done making breaking changes
During the release candidate cycle, we are completing all remaining tasks necessary to publish v1.0.0 GA.
The Redwood Core Team is working publicly — progress is updated daily on the Release Project Board. There’s also a Triage Board, including an important tab view of Issues that are priorities but need community help.
- 👉 Start here: v1 Help Wanted tab on the Triage Project Board (sorted by difficulty)
Eventually, all this leads you back to Redwood’s GitHub Issues page. Here you’ll find open items that need help, which are organized by labels. There are four labels helpful for contributing:
- Good First Issue: these items are more likely to be an accessible entry point to the Framework. It’s less about skill level and more about focused scope.
- Help Wanted: these items especially need contribution help from the community.
- v1 Priority: to reach Redwood v1.0.0, we need to close all Issues with this label.
- Bugs 🐛: Last but not least, we always need help with bugs. Some are technically less challenging than others. Sometimes the best way you can help is to attempt to reproduce the bug and confirm whether or not it’s still an issue.
The sweet spot is a “v1 Priority” Issue that’s either a “Good First Issue” or “Help Wanted”. Yes, please!
# Create a New Issue
Anyone can create a new Issue. If you’re not sure that your feature or idea is something to work on, start the discussion with an Issue. Describe the idea and problem + solution as clearly as possible, including examples or pseudo code if applicable. It’s also very helpful to
@ mention a maintainer or Core Team member that shares the area of interest.
Just know that there’s a lot of Issues that shuffle every day. If no one replies, it’s just because people are busy. Reach out in the Forums, Chat, or comment in the Issue. We intend to reply to every Issue that’s opened. If yours doesn’t have a reply, then give us a nudge!
Lastly, it can often be helpful to start with brief discussion in the community Chat or Forums. Sometimes that’s the quickest way to get feedback and a sense of priority before opening an Issue.
# Contributing Code
Redwood's composed of many packages that are designed to work together. Some of these packages are designed to be used outside Redwood too!
Before you start contributing, you'll want to set up your local development environment. The Redwood repo's top-level contributing guide walks you through this. Make sure to give it an initial read.
For details on contributing to a specific package, see the package's README (links provided in the table below). Each README has a section named Roadmap. If you want to get involved but don't quite know how, the Roadmap's a good place to start. See anything that interests you? Go for it! And be sure to let us know—you don't have to have a finished product before opening an issue or pull request. In fact, we're big fans of Readme Driven Development.
What you want to do not on the roadmap? Well, still go for it! We love spikes and proof-of-concepts. And if you have a question, just ask!
# RedwoodJS Framework Packages
||Run a Redwood app using Express server (alternative to serverless API)|
||Infrastruction components for your applications UI including logging, webhooks, authentication decoders and parsers, as well as tools to test custom serverless functions and webhooks|
||A lightweight wrapper around popular SPA authentication libraries|
||All the commands for Redwood's built-in CLI|
||Defines babel plugins and config files|
||Configuration for the local development server|
||Defines Redwood's eslint config|
||Defines eslint plugins; currently just prohibits the use of non-existent pages in
||Provides Form helpers|
||Exposes functions to build the GraphQL API, provides services with
||Provides tooling to parse Redwood configs and get a project's paths|
||The built-in router for Redwood|
||Provides a way to build, validate and inspect an object graph that represents a complete Redwood project|
||Provides helpful defaults when testing a Redwood project's web side|
||Configures a Redwood's app web side: wraps the Apollo Client in
# Contributing Docs
First off, thank you for your interest in contributing docs! Redwood prides itself on good developer experience, and that includes good documentation.
Before you get started, there's an implicit doc-distinction that we should make explicit: all the docs on redwoodjs.com are for helping people develop apps using Redwood, while all the docs on the Redwood repo are for helping people contribute to Redwood.
Although Developing and Contributing docs are in different places, they most definitely should be linked and referenced as needed. For example, it's appropriate to have a "Contributing" doc on redwoodjs.com that's context-appropriate, but it should link to the Framework's CONTRIBUTING.md (the way this doc does).
# How Redwood Thinks about Docs
Before we get into the how-to, a little explanation. When thinking about docs, we find divio's documentation system really useful. It's not necessary that a doc always have all four of the dimensions listed, but if you find yourself stuck, you can ask yourself questions like "Should I be explaining? Am I explaining too much? Too little?" to reorient yourself while writing.
# Docs for Developing Redwood Apps
redwoodjs.com has three kinds of Developing docs: Docs, Cookbook Recipes, and The Tutorial. You can find Docs and Cookbook Recipes within their respective directories on the redwood/redwoodjs.com repo: docs/ and cookbook/. The Tutorial is actually all in one file.
The Tutorial is a standalone document that serves a specific purpose as an introduction to Redwood, an aspirational roadmap, and an example of developer experience. As such, it's distinct from the categories mentioned, although it's most similar to Cookbook Recipes.
Docs are explanation-driven how-to content. They're more direct and to-the-point than The Tutorial and Cookbook Recipes. The idea is much more about finding something or getting something done than any kind of learning journey.
Before you take on a doc, you should read Form and Redwood Router; they have the kind of content you should be striving for. They're comprehensive yet conversational.
In general, don't be afraid to go into too much detail. We'd rather you err on the side of too much than too little. One tip for finding good content is searching the forum and repo for "prior art"—what are people talking about where this comes up?
# Cookbook Recipes
Cookbook Recipes are tutorial-style content focused on a specific problem-solution. They usually have a beginner in mind (if not, they should indicate that they don't—put 'Advanced' or 'Deep-Dive', etc., in the title or introduction). Cookbook Recipes may include some explanatory text as asides, but they shouldn't be the majority of the content.
# Making a Doc Findable
If you write it, will they read it? We think they will—if they can find it.
After you've finished writing, step back for a moment and consider the word(s) or phrase(s) people will use to find what you just wrote. For example, let's say you were writing a doc about configuring a Redwood app. If you didn't know much about configuring a Redwood app, a heading (in the nav bar to the left) like "redwood.toml" wouldn't make much sense, even though it is the main configuration file. You'd probably look for "Redwood Config" or "Settings", or type "how to change Redwood App settings" in the "Search the docs" bar up top, or in Google.
That is to say, the most useful headings aren't always the most literal ones. Indexing is more than just underlining the "important" words in a text—it's identifying and locating the concepts and topics that are the most relevant to our readers, the users of our documentation.
So, after you've finished writing, reread what you wrote with the intention of making a list of two to three keywords or phrases. Then, try to use each of those in three places, in this order of priority:
- the left-nav menu title
- the page title or the first right-nav ("On this page") section title
- the introductory paragraph
# Docs for Contributing to the Redwood Repo
These docs are in the Framework repo, redwoodjs/redwood, and explain how to contribute to Redwood packages. They're the docs linked to in the table above.
In general, they should consist of more straightforward explanations, are allowed to be technically heavy, and should be written for a more experienced audience. But as a best practice for collaborative projects, they should still provide a Vision + Roadmap and identify the project-point person(s) (or lead(s)).
# What makes for a good Pull Request?
In general, we don’t have a formal structure for PRs. Our goal is to make it as efficient as possible for anyone to open a PR. But there are some good practices, which are flexible. Just keep in mind that after opening a PR there’s more to do before getting to the finish line:
- Reviews from other contributors and maintainers
- Update code and, after maintainer approval, merge-in changes to the
- Once PR is merged, it will be released and added to the next version Release Notes with a link for anyone to look at the PR and understand it.
Some tips and advice:
- Connect the dots and leave a breadcrumb: link to related Issues, Forum discussions, etc. Help others follow the trail leading up to this PR.
- A Helpful Description: What does the code in the PR do and what problem does it solve? How can someone use the code? Code sample, Screenshot, Quick Video… Any or all of this is so so good.
- Draft or Work in Progress: You don’t have to finish the code to open a PR. Once you have a start, open it up! Most often the best way to move an Issue forward is to see the code in action. Also, often this helps identify ways forward before you spend a lot of time polishing.
- Questions, Items for Discussion, Etc.: Another reason to open a Draft PR is to ask questions and get direction via review.
- Loop in a Maintainer for Feedback and Review: ping someone with an
@. And nudge again in a few days if there’s no reply. We appreciate it and truly don’t want the PR to get lost in the shuffle!
- Next Steps: Once the PR is merged, will there be a follow up step? If so, link to an Issue. How about Docs to-do or Docs to-merge?
The best thing you can do is look through existing PRs, which will give you a feel for how things work and what you think is helpful.
# Example PR
If you’re looking for an example of “what makes a good PR”, look no further than this one by Kim-Adeline:
Not every PR needs this much information. But it’s definitely helpful when it does!