|
13 | 13 |
|
14 | 14 | ## About |
15 | 15 |
|
16 | | -CedarJS is a fork of the [RedwoodJS](https://redwoodjs.com/) framework with the |
17 | | -goal of taking it into the modern web development era with a smooth transition |
18 | | -path for existing RedwoodJS applications. |
19 | | - |
20 | | -CedarJS is a reliable, modern, and actively maintained full-stack React |
21 | | -framework used in production by both large and small companies. |
| 16 | +CedarJS is an opinionated, full-stack React framework that makes building web |
| 17 | +applications fast and enjoyable. It includes everything you need: React for the |
| 18 | +frontend, GraphQL for the API, Prisma for the database, and built-in support |
| 19 | +for authentication, testing, and deployment. |
| 20 | + |
| 21 | +CedarJS is a fork of the |
| 22 | +[RedwoodJS GraphQL](https://github.com/redwoodjs/graphql) framework that is |
| 23 | +actively maintained and used in production by companies of all sizes. With |
| 24 | +active development focused on modern web standards and developer experience, |
| 25 | +Cedar is evolving with new features and improvements that aren't available in |
| 26 | +RedwoodJS. |
22 | 27 |
|
23 | 28 | CedarJS would obviously not be where it is today without the vision and heroic |
24 | 29 | efforts of the RedwoodJS founders, maintainers and community. |
25 | 30 |
|
26 | 31 | > cedar has become a powerful symbol of strength and revitalization\ |
27 | 32 | > _— https://indigenousfoundations.arts.ubc.ca/cedar/_ |
28 | 33 |
|
| 34 | +## Why Cedar? |
| 35 | + |
| 36 | +### For RedwoodGraphQL (formerly RedwoodJS) Users |
| 37 | + |
| 38 | +If you're currently using RedwoodGraphQL, here's why you might want to consider |
| 39 | +Cedar: |
| 40 | + |
| 41 | +- Cedar is actively maintained by developers who use it in production daily. New |
| 42 | + features, bug fixes, and security updates are consistently delivered. |
| 43 | +- Cedar includes improvements and features that aren't available in RedwoodJS, |
| 44 | + like |
| 45 | + [Recurring Jobs](https://cedarjs.com/docs/background-jobs/#recurring-jobs) and |
| 46 | + [experimental ESM support](https://github.com/cedarjs/cedar/tree/f824d9dbd87965fa96c9b7a06f62a14dc7f5b0a1/packages/create-cedar-app/templates/esm-ts). |
| 47 | +- Moving toward ESM-only packages and modern JavaScript standards to |
| 48 | + future-proof your applications. |
| 49 | +- Cedar maintains backward compatibility with RedwoodJS |
| 50 | + v8.6, making migration straightforward with a clear upgrade path. |
| 51 | + |
| 52 | +### For Everyone Else |
| 53 | + |
| 54 | +Whether you're building a startup MVP, a departmental tool, or a full production |
| 55 | +application, here's what you get with Cedar: |
| 56 | + |
| 57 | +- Fast Setup. Get from zero to deployed application with a database in minutes, |
| 58 | + not days. |
| 59 | +- An extensive CLI with generator and setup commands for most things you want to |
| 60 | + do. A dedicated CLI is faster and cheaper than asking AI to do it for you, and |
| 61 | + 100% predictable. |
| 62 | +- Team empowerment. Keep your entire stack in TypeScript/JavaScript. No context |
| 63 | + switching between languages or separate teams for frontend and backend. |
| 64 | + Everyone is empowered to contribute across the entire application. |
| 65 | +- Architectural decisions made for you, so you don't get stuck in analysis |
| 66 | + paralysis or get decision fatigue. But it doesn't lock you in. You have full |
| 67 | + control over your code, your auth, your database, and your deployment. |
| 68 | +- Ready made integrations for hosting on Vercel, Netlify, AWS, Render, or your |
| 69 | + own servers. Switch providers easily without major rewrites. |
| 70 | +- A production ready framework. Used by companies in production with a mature |
| 71 | + ecosystem and comprehensive documentation. |
| 72 | +- You start with a working app that includes routing, database setup, and |
| 73 | + testing – all configured and ready to go. And if there's more you need, like |
| 74 | + authorization, there's most likely a setup command or a generator for it. |
| 75 | + |
| 76 | +### Who Is Cedar For? |
| 77 | + |
| 78 | +Cedar is ideal for: |
| 79 | + |
| 80 | +**Startups** that need to move fast and iterate quickly. **Solo developers** who |
| 81 | +want to build full-stack apps without managing complex tooling. **Development |
| 82 | +teams** that value standardization and clear conventions. **Companies** |
| 83 | +transitioning from RedwoodJS or looking for an actively maintained full-stack |
| 84 | +framework with a dedicated API layer. Or just about **anyone** who wants to |
| 85 | +focus on building features rather than configuring build tools and |
| 86 | +infrastructure |
| 87 | + |
29 | 88 | ## Migrating from RedwoodJS to CedarJS |
30 | 89 |
|
31 | 90 | 1. Search and replace all instances of `"@redwoodjs/(.*)": "\d+\.\d+\.\d+"` |
|
0 commit comments