From f71d08f0f8deb688733f781d15fb2a95baaedb02 Mon Sep 17 00:00:00 2001 From: Diversable Date: Wed, 22 Nov 2023 12:49:49 -0800 Subject: [PATCH] address PR comments by @reedwoodruff --- docs/book/src/csr_wrapping_up.md | 2 +- docs/book/src/getting_started/README.md | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/book/src/csr_wrapping_up.md b/docs/book/src/csr_wrapping_up.md index a21e81cbbf..b34c50468c 100644 --- a/docs/book/src/csr_wrapping_up.md +++ b/docs/book/src/csr_wrapping_up.md @@ -3,7 +3,7 @@ So far, everything we’ve written has been rendered almost entirely in the browser. When we create an app using Trunk, it’s served using a local development server. If you build it for production and deploy it, it’s served by whatever server or CDN you’re using. In either case, what’s served is an HTML page with 1. the URL of your Leptos app, which has been compiled to WebAssembly (WASM) -2. the URL of the JavaScript used to initialized this WASM blob +2. the URL of the JavaScript used to initialize this WASM blob 3. an empty `` element When the JS and WASM have loaded, Leptos will render your app into the ``. This means that nothing appears on the screen until JS/WASM have loaded and run. This has some drawbacks: diff --git a/docs/book/src/getting_started/README.md b/docs/book/src/getting_started/README.md index cff52450b3..3fa780b9ba 100644 --- a/docs/book/src/getting_started/README.md +++ b/docs/book/src/getting_started/README.md @@ -12,11 +12,11 @@ We’ll introduce `cargo-leptos` in Part 2 of this book, which is all about work ```admonish note If you're coming from the Javascript world and terms like Client-Side Rendering (CSR) and server-side rendering (SSR) are unfamiliar to you, the easiest way to understand the difference is by analogy: -CSR is similar to working with React (or a 'signals'-based framework like SolidJS), and focuses on producing a client-side UI which you can use with any tech stack on the server. +Leptos' CSR mode is similar to working with React (or a 'signals'-based framework like SolidJS), and focuses on producing a client-side UI which you can use with any tech stack on the server. -SSR is like working with a full-stack framework like Next.js in the React world (or Solid's "SolidStart" framework) - SSR helps you build sites and apps using JS on both the client and the server. +Using Leptos' SSR mode is similar to working with a full-stack framework like Next.js in the React world (or Solid's "SolidStart" framework) - SSR helps you build sites and apps that are rendered on the server then sent down to the client. SSR can help to improve your site's loading performance and accessibility as well as make it easier for one person to work on *both* client- and server-side without needing to context-switch between different languages for frontend and backend. -Leptos is similar: you can use it to either just make your UI, or you can use full-stack / 'Universal' Leptos to build an app powered by Rust on both client and server. +The Leptos framework can be used either in CSR mode to just make a UI (like React), or you can use Leptos in full-stack / 'Universal' mode (like Next.js) so that you can build both your UI and your server with one language: Rust. ``` @@ -117,4 +117,4 @@ Welcome to the world of UI development with Rust and WebAssembly (WASM), powered --- -Now before we get started building your first real UI's with Leptos, there's a couple of things you might want to know to help make your experience with Leptos just a little bit easier. \ No newline at end of file +Now before we get started building your first real UI's with Leptos, there are a couple of things you might want to know to help make your experience with Leptos just a little bit easier. \ No newline at end of file