You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the addition of render modes and per-page interactivity, the template has grown too complex for new users of the framework. Users have to make a choice between:
Per page interactivity vs Global interactivity
SSR, Server, WebAssembly or a combination thereof.
Auth options
This can be challenging (specially the render modes and per page vs global interactivity) and might not be optimal for newcomers to the framework.
While we want to retain all these options in the template, however, it might be good if we can create "blessed paths" within the template/UI to some of the most popular combinations (Global interactivity + Wasm + Prerendering (Hosted wasm)) and (Global interactivity + Server + No-Prerendering) + auth options.
An alternative might be a different experience that provides more information inline to make a decision or a "quickstart" template that doesn't give you options (or only gives you server/client) so that you can get started quickly and leave the existing template as it is.
Another alternative is to remove all the options (except for the most basic ones) from the template and use scaffolders to bring in functionality as needed.
The text was updated successfully, but these errors were encountered:
With the addition of render modes and per-page interactivity, the template has grown too complex for new users of the framework. Users have to make a choice between:
This can be challenging (specially the render modes and per page vs global interactivity) and might not be optimal for newcomers to the framework.
While we want to retain all these options in the template, however, it might be good if we can create "blessed paths" within the template/UI to some of the most popular combinations (Global interactivity + Wasm + Prerendering (Hosted wasm)) and (Global interactivity + Server + No-Prerendering) + auth options.
An alternative might be a different experience that provides more information inline to make a decision or a "quickstart" template that doesn't give you options (or only gives you server/client) so that you can get started quickly and leave the existing template as it is.
Another alternative is to remove all the options (except for the most basic ones) from the template and use scaffolders to bring in functionality as needed.
The text was updated successfully, but these errors were encountered: