docs: add new project types page #13444
Conversation
|
|
||
| By default, when a user visits a site, SvelteKit will render the first page with server-side rendering and subsequent pages with client-side rendering. Using SSR for the initial render improves SEO and perceived performance of the initial page load. Client-side rendering then takes over and updates the page without having to rerender common components which is typically faster and eliminates a flash when navigating between pages. | ||
|
|
||
| ## Static site generator (SSG) |
There was a problem hiding this comment.
It bothers me that the format of these headers is different...
Should it be:
- Default: Hybrid rendering
- Static site generation (SSG)
- Single-page app (SPA)
?
There was a problem hiding this comment.
Even that doesn't feel quite right, struggling with how to align them
There was a problem hiding this comment.
I'm not sure what you mean that the format is different? Like you think they all need to end in "app"? The only one that feels a bit different from the rest to me is "Backend in another language", but I'm not sure how else to write that and think it's worth keeping given how many people want to do that and run into it
| In order to support SSR, a JS backend — such as Node.js or Deno-based server, serverless function, or edge function — is required. | ||
|
|
||
| It is also possible to write custom adapters or leverage community adapters to deploy SvelteKit to more platforms such as specialized server environments, browser extensions, or native applications. See [integrations](./integrations) for more examples and integrations. | ||
| See [the documentation regarding project types] for more details. |
There was a problem hiding this comment.
Incomplete link
elliott-with-the-longest-name-on-github
dismissed
their stale review
accidentally approved
Co-authored-by: Elliott Johnson <sejohnson@torchcloudconsulting.com>
|
Co-authored-by: Elliott Johnson <sejohnson@torchcloudconsulting.com>
Co-authored-by: Elliott Johnson <sejohnson@torchcloudconsulting.com>
Co-authored-by: Elliott Johnson <sejohnson@torchcloudconsulting.com>
|
This definitely helps. Maybe define terms such as SPA? My problem before was there are many architectural options and getting what concepts the team have in mind was not easy. This does help address that. For example here's the architectural options I'm aware of and I tried to fit terms like CSR and SSR into that model. Server pages (routes) and RESTful endpoints such as APIs
Edge
Client
|
Co-authored-by: Enrico Sacchetti <enrico@theetrain.ca>
Co-authored-by: Enrico Sacchetti <enrico@theetrain.ca>
|
Any consideration on reusing terms from this page Or a graph like this one to outline how the options map to each? |
This seems to be the area where I most frequently see new comers having difficulty. A standalone page with more details may be in order as I think the FAQ is not helping enough