Most open source projects follow common structure. You put your source files under "src", distribution files go to "dist", unit tests under "tests". Nothing wrong with that, so I mostly followed it for Blogifier and ended up with this structure.
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.
There is new theme added to Blogifier that has only two purposes in life - to provide clean, easiest possible HTML5 template for building your own theme from scratch and to run optimization tests
The custom fields is not a new concept in Blogifier, I've wrote about it long ago and it exists and used in the current code base. It looks somewhat like this:
I thought it will take a whole lot more, but it was surprisingly easy. The big restructure I wanted to do for the Blogifier repository took just a couple of days to complete; splitting into multiple repositories, cleaning and making it all work with each other and publishing to Nuget.org as reusable libraries.
Blogifier Restructuring Plans, creating new Blogifier.Blazor, splitting core functionality into components
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.
