Reference | RedwoodJS Docs

📄️ Accessibility (aka a11y)

Accessibility is a core feature that's built-in

📄️ Assets and Files

How to include assets—like images—in your app

No one likes waiting in line. This is especially true of your website: users don't want to wait for things to load that don't directly impact the task they're trying to accomplish. For example, sending a "welcome" email when a new user signs up. The process of sending the email could take as long or longer than the sum total of everything else that happens during that request. Why make the user wait for it? As long as they eventually get the email, everything is good.

📄️ Builds

What happens when you build your app

📄️ Cells

Declarative data fetching with Cells

📄️ Command Line Interface

A comprehensive reference of Redwood's CLI

📄️ Connection Pooling

Scale your serverless functions

📄️ Contributing

There's several ways to contribute to Redwood

📄️ Contributing Walkthrough

Watch a video of the contributing process

📄️ Cross-Origin Resource Sharing

For when you need to worry about CORS

📄️ Create Redwood App

Instructions and usage examples for Create Redwood App

📄️ Data Migrations

Track changes to database content

🗃️ Deployment

9 items

📄️ Database Seeds

Seeds are data that are required in order for your app to function. Think of

📄️ Directives

Customize GraphQL execution

📄️ Docker

Redwood's Dockerfile

📄️ Environment Variables

How to use environment variables on the api and web sides

📄️ Forms

Redwood makes building forms easier with helper components

🗃️ GraphQL

6 items

📄️ Local Postgres Setup

Setup a Postgres database to develop locally

📄️ Logging

Use the Logger to observe your application

📄️ Mailer

RedwoodJS offers a convenient Mailer for sending emails to your users. It's not just about sending an email; delivery matters too. The way you deliver the feature requiring email is as significant as how you prepare the mail to be delivered by the infrastructure that sends emails over the internet.