Back to basics here. When you have a .NET application and want to add class library to the solution, it will be added as a standard class library. What it means is the project file will have this markup right on top.
If you watched brilliant as always presentation Steve Sanderson gave at recent Build about Blazor WebAssembly release to the world, you probably getting curious and tempted to kick the tires on that new shiny thing.
Main change in this release is moving to decoupled architecture, with APIs providing access to front-end clients. It is not headless - there web application with administration and content management, but blog itself can be anything.
Angular Theme for Blogifier - Dynamic Data. To streamline development, I'm going to use data service from existing Blogifier theme. So I go and grab it from here and copy to `src/app/core`. One thing to fix right away is to modify environment files to include API endpoint required by service I just imported. Because our theme uses public APIs, we can point it to any Blogifier instance.
In this part we'll get to coding, so VS Code or other editor with Angular support highly recommended. I'll use VS Code here. Install if not already and open folder from the first tutorial, `C:\demo\myapp`. In the terminal, run `ng serve` to make sure it builds and runs application with no errors. You should see something similar to below.
This is the first tutorial, its goal to help understand how theming engine works in Blogifeir and get started on theme development quickly and easily. Tutorial does not get into much details, just steps through creating and deploying Angular CLI application as Blogifier theme.
Looking at the latest in web design, it seems that focus is shifting from HTML-based themes to creating complex client-side applications with React, Angular, Vue and so on. This is natural progression as all those frameworks mature and provide more power in hands of front-end developers.
Tonight I released Blogifier 2.1. I also installed it on couple sites that I'm going to support moving forward. Having multiple instances running in production environment puts a lot of restrictions, because support and maintenance on the live site takes a lot of time and effort.