Few seconds in and I already appreciate the photography, "Oh, hi. I didn't see you there", so personal and the warm clear voice. Can't wait to learn more about RedwoodJS
Extremely great, smooth and clear video tutorial! Can't wait for the following episodes! I am now following Redwood tutorials for my next side project (currently struggling with converting JS to TS). Please keep up the great work!
If you liked part one check out part 2 where we actually start talking to the database! We've got even more opinions! :) ruclips.net/video/SP5vbsWf5Yg/видео.html
This is so nicely structured and well though. I just wish you preferred Svelte over React. Great patterns nonetheless... Redwood has the potential to become the best framework out there.
Not at the moment, no. We'd definitely like to get pre-rendering support in the near future for mostly static pages, but full-on server-side rendered is tough-we're focusing on connecting you to a live database where the data will be constantly changing.
@@facinick Not sure what you mean by multi-page app: Redwood uses React so it's always a single page app. We have the concept of "pages" which you'd usually create for every URL in your app, but all URLs are going actually being routed to /index.html where React takes over and renders the appropriate page. As for PWAs, we don't have anything special for offline support, push notifications or anything like that (yet).
@@facinick Tons of people are building SaaS apps with Redwood right now, it's probably one of the main usecases. One of the founders is building www.snaplet.dev/ as we speak!
So, what is it in fact and why would anyone use it exactly? After 10 minutes all you have is still just a white page. Wix and Squarespace look much easier to create web pages quickly, with data.
If you're just looking to make a website with some text and images then this framework is definitely not for you! This is more for professional developers to make a website that talks to a database where everything is built from scratch. There are lots of frameworks out there to do this already, but Redwood does some things differently and, we hope, easier than others.
@@cannikinn Thanks. I'm pretty sure though that pros don't bind a UI framework directly to a DB for obvious performance and scalability issues, even for low volume web sites or apps.
It's not bound directly, everything goes through a GraphQL API! In Redwood both the API and the frontend are monorepos in the same codebase. So they're completely separate from each other, but still live within the same codebase for simplicity. You could deploy only one or the other, but a service like Netlify makes it really simple to do both.
Few seconds in and I already appreciate the photography, "Oh, hi. I didn't see you there", so personal and the warm clear voice. Can't wait to learn more about RedwoodJS
Extremely great, smooth and clear video tutorial! Can't wait for the following episodes! I am now following Redwood tutorials for my next side project (currently struggling with converting JS to TS). Please keep up the great work!
Part 2 just went live! ruclips.net/video/SP5vbsWf5Yg/видео.html
I love the generators and how opinionated everything is!
If you liked part one check out part 2 where we actually start talking to the database! We've got even more opinions! :) ruclips.net/video/SP5vbsWf5Yg/видео.html
This is so nicely structured and well though. I just wish you preferred Svelte over React. Great patterns nonetheless... Redwood has the potential to become the best framework out there.
Great video. Looking forward to the follow on tutorial videos :D
Part 2 just went live! ruclips.net/video/SP5vbsWf5Yg/видео.html
What theme are you using?
VS Code Theme? That's Material Theme Darker High Contrast, I love it! material-theme.site/
@@cannikinn Awesome. Thanks!
create redwood-app ./my-redwood-project but not install , i have already install node , yarn and npm please send me process link.
Is this server side rendered?
Not at the moment, no. We'd definitely like to get pre-rendering support in the near future for mostly static pages, but full-on server-side rendered is tough-we're focusing on connecting you to a live database where the data will be constantly changing.
another framework to learn
typescript?
Yup, the entire framework is typed and we even support TS in the generators, just add the `--typescript` flag!
@@cannikinn Also, I’ve seen so many examples of multi page webapps, how is redwood js for a single page app and PWAs?
What about SAAS Applications?
@@facinick Not sure what you mean by multi-page app: Redwood uses React so it's always a single page app. We have the concept of "pages" which you'd usually create for every URL in your app, but all URLs are going actually being routed to /index.html where React takes over and renders the appropriate page. As for PWAs, we don't have anything special for offline support, push notifications or anything like that (yet).
@@facinick Tons of people are building SaaS apps with Redwood right now, it's probably one of the main usecases. One of the founders is building www.snaplet.dev/ as we speak!
So, what is it in fact and why would anyone use it exactly? After 10 minutes all you have is still just a white page.
Wix and Squarespace look much easier to create web pages quickly, with data.
If you're just looking to make a website with some text and images then this framework is definitely not for you! This is more for professional developers to make a website that talks to a database where everything is built from scratch. There are lots of frameworks out there to do this already, but Redwood does some things differently and, we hope, easier than others.
@@cannikinn Thanks. I'm pretty sure though that pros don't bind a UI framework directly to a DB for obvious performance and scalability issues, even for low volume web sites or apps.
It's not bound directly, everything goes through a GraphQL API! In Redwood both the API and the frontend are monorepos in the same codebase. So they're completely separate from each other, but still live within the same codebase for simplicity. You could deploy only one or the other, but a service like Netlify makes it really simple to do both.