Template UX refresh

[javiercn]

This issue tracks the changes to the templates in the .NET 7.0 timeframe. This includes things like updating Bootstrap and any refresh to the look and feel in the templates we want to do.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[GiorgioG]

Any chance that bootstrap & jquery are ditched for something more modern? The current template feels like it just walked out of 2010. Tailwind & Alpine.js seem much more appropriate/modern options.

[lonix1]

Actually the latest version of Bootstrap doesn't use jQuery. So the only reason to use jQuery is for "jQuery Validation" and "jQuery Validation Unobtrusive", both of which work but are old and gnarly (especially the latter, which needs work). Maybe there's a modern/better validation library that doesn't need jQuery.

[TanayParikh]

Cross linking: #37199

[TanayParikh]

Related:

• Replace outdated dependencies in Blazor Server project template #44606
• Update the ASP.NET Core hosted Blazor WebAssembly template to use _Host.cshtml #25631

[lonix1]

If you don't replace the "jQuery Validate Unobtrusive" plugin, please remember that it needs work - see here (that issue should not have been closed).

Ideally a better way is needed. As I noted above, Bootstrap no longer uses jQuery, which means no more jQuery Validate, which means no more jQuery Validate Unobtrusive.

[codemonkey85]

One thing I'd like to see is a change from packaging a specific version of bootstrap / open iconic to relying on libman and specifying the version number there. That would make it easier to change or update the version being used from the template, after creating a new project.

[mrlife]

Are there any plans to consider using https://github.com/microsoft/fast or https://github.com/microsoft/fast-blazor?

[Lumethys]

an idea is to look at other frameworks are doing: A option in the scaffolding would be the best option, let the dev decide whether they like jquery, alpine or some sort of blazor WASM solution

[FabianAronsson]

an idea is to look at other frameworks are doing: A option in the scaffolding would be the best option, let the dev decide whether they like jquery, alpine or some sort of blazor WASM solution

I agree. Different projects require different implementations and it should be easy to choose what your specific project needs.
Keep Bootstrap, but perhaps refresh it a little and also add some other new popular framework.

[mkArtakMSFT]

Moving this as we didn't get to updating the templates in .NET 8. Moving to .NET 9.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[lonix1]

If you can't work on updating the templates within your project schedule for .NET8, fine.

But, please at least consider replacing the jquery + jquery validate + jquery unobtrusive validation libraries. They are archaic, deprecated and add significant friction. We're talking about seriously out-of-date libraries.

A number of alternatives were proposed above. The best "drop in" replacement for aspnet is the one by Phil Haack.

Just the libraries themselves. Leave template changes to a future date when you can work on them.

[Alerinos]

@lonix1 You can do the implementation of the libraries yourself. Besides, you don't use jquery anymore. In addition, we now have WebAssembly Blazor which is being heavily developed. The change was only supposed to be about cosmetics of the finished template.

[lonix1]

The change was only supposed to be about cosmetics

No, read the OP and various issues which were closed and redirected to this one. It's about handling decade-old hard to use js dependencies; this is not just about cosmetics.

[GiorgioG]

I wont even consider using the ASP.NET identity templates because they still depend on jQuery. It’s 2023, not 2013.

[ghost]

We have CSS Grid / Flexbox / CSS Variables and a lot of things else; I don't understand why people prefer to install things with more complexities to use ... Bootstrap and jQuery... Why? jQuery, we have Alpine.JS / HTMX (also good for simple things) for people that do not like the weird JavaScript like me. But TS makes JS more pleasurable not like the beauty of CSharp but more pleasure with types... "Blazor United we are waiting for you XDD \o/". So, jQuery we understand, because a lot of people do not like JS, but like I said Alpine and HTMX resolve what is needed. Bootstrap I don't understand. When I'm going to buy a course and I see bootstrap I go next... I learned Bootstrap once, before modern CSS layouts to be introduced. Even so, I didn't like it. Because I must use a class created for others, install packages, following rules that change version to version ... But today... display: grid only with these things already get better lol .... we do use frameworks outside; the company I work for, we use Vanilla HTML / Vanilla CSS / Alpine - Vanilla JS (for quite simple tasks), we work with Sveltekit (with Typescript) for a good part of company work (for things that need to be dynamics; interactivity). and for large things the company I work rely on .NET Razor Pages, and now that with Minimal API with svelte became a wonderful thing that we got the authorization to use, and understand (but Blazor United can be the new kid on the ground for us) in this area ... In the company I work for, we follow a rule that is: less inside template, do you want to use Bootstrap makes easy installation, do not make the developer swallow it out of the box, want jQuery (or better saying Alpine) make easy installation. Like Sveltekit that makes simple, want TS ? say Y (yes), want prettier? say Y (yes) etc. ...

ps.: I know that some people work a long date with bootstrap each version things get better, seems like today flexbox is inside, but; to give option before to create template is the way to go ...

[mkArtakMSFT]

Closing as a dupe of #53142

[lonix1]

@mkArtakMSFT That issue is for blazor, this is for the mvc/razorpages templates in general. Please don't let this issue fall off the radar.