Summary

In this chapter, we have added shared CSS.

We saw how to create shared libraries (for others to use). This is also a great way to structure our in-house projects (so that it is easy to change from Blazor Server to Blazor WebAssembly, or the other way around).

If you have a site already, you can build your Blazor components in a shared library, which we have done throughout the book.

Using components as part of your site (using Blazor Server), you can get started with Blazor bit by bit until you have converted the whole thing. When that is done, you can decide whether or not to keep using Blazor Server (as I mentioned, we use Blazor Server at my workplace) or move to Blazor WebAssembly, or use both as our project does.

We talked about how we can use SASS and CSS in our site, both regular CSS and isolated CSS.

In the next chapter, we will learn about the one thing we are trying to avoid (at least, I am) as Blazor developers – JavaScript.