dotnet / dotnet/aspnetcore

[Blazor] Better workflow for template creation

Open
#60,311 0 comments 5 reactions 0 assignees View on GitHub
area-blazor
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 6h
Merged PRs (30d)
290

Description

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.