This is a T3 Stack project bootstrapped with create-t3-app.
We try to keep this project as simple as possible, so you can start with just the scaffolding we set up for you, and add additional things later when they become necessary.
If you are not familiar with the different technologies used in this project, please refer to the respective docs. If you still are in the wind, please join our Discord and ask for help.
Some packages in the standard t3 stack have been replaced for this project, and some additional packages included. Also some tools configured for easy deployment with show up in platform configuration and aren't really in the code/this repo, but can serve as a fast road to deployment, so mentioned here for reference.
A UI component library with a great react component feel. Simple and extensible. Probably less configurable than tailwind, but can get to decent looking styles fast with little to no css
Git hooks for automating certain actions. Currently set to automatically lint git staged files before a git commit is executed, ensuring cross team code conformity. Can be used to ensure automated tests are run and passing before committing too.
Typed object validation. Used particularly on input data from forms, or data retrieved from the database. The combination of this and tRPC allows for consistently typed data across all stages of the application, traversing backend and frontend interactions.
With SWR, components will get a stream of data updates constantly and automatically. And the UI will be always fast and reactive. The name “SWR” is derived from stale-while-revalidate, a HTTP cache invalidation strategy popularized by HTTP RFC 5861(opens in a new tab). SWR is a strategy to first return the data from cache (stale), then send the fetch request (revalidate), and finally come with the up-to-date data.
Serverless hosting and CI/CD. Provides integrations to many of the other 3rd party serverless hosted solutions mentioned below.
A 3rd party authentication provider, enabling multiple authentication methods. From socials (twitter, github, facebook), to email, to metamask. Currently configured use a wide array of socials and metamask, but no email or sign up based authentication (wan't to avoid ever storing passwords if at all possible).
3rd party hosted serverless database. Integrates nicely with prisma and vercel. Treats it pretty much as MySql, but technically slightly different under the hood? Apparently shouldn't need to worry about that?
3rd party hosted serverless logging. Better searchability and other features than the standard logging provided by Vercel.
Serverless solution for Redis and Kafka. Add if required.
Also configured to use Prettier along with ESLint for linting. Makefile not yet working, but will be set up to provide convenience alternatives to package.json scripts which are abstracted away from the specific tool invocations.
To learn more about the T3 Stack, take a look at the following resources:
You can check out the create-t3-app GitHub repository — your feedback and contributions are welcome!
Follow our deployment guides for Vercel, Netlify and Docker for more information.