It sounds reasonable - why would I want to pay for something I'm not using, right? Well, there is a catch - you pretty much signing in for a lottery. And I "won". Twice.
Few weeks back I upgraded this blog to run on Blogifier - open source project I put on Github over a year ago. In its current incarnation it is a small blogging application that is fun and easy to use - to me at least :)
It is very much in your face but so sudden that it took me awhile to realize. You may be familiar with this from VS Code - the minimap on the side of code window displaying quick preview. It can be helpful and some people like using it, but over time I wanted go back to minimalistic editor and remove this feature.
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.
There is decent amount of documentation on how to install, configure and run .NET Core on Linux, but most of it pretty generic and may be a little overwhelming when you trying to accomplish specific and relatively simple task.
For a while Blogifier tried wearing two hats - been platform (Core) and application at the same time. In theory it made sense, in reality you need large team for this kind of multitasking.
Explaining is hard. Things that seem crystal clear to you can be completely foreign to others, and when I started planning on Blogifier, concept looked very natural and not even worth explanation.
It took just a few weeks to move Blogifier to release 1.1. Although changes are mostly cosmetic, it adds some really nice polishing touches to core functionality and significantly improves UX. Check out below what exactly was added in this new version.
It took way too long but finally Blogifier.Core 1.0 has been released to the world! It means, two brand new packages popped up in the Nuget.org and, if you search on "blogifier" it should return page looking similar to this
People keep sending me emails asking if BlogEngine.NET is dead. Not surprisingly, given lack of updates since beginning of 2017. So what's going on? As they say, picture worth a thousand words, this one explains where things stand now pretty accurately.
I've been playing with this idea for a while now, trying different approaches, building proof of concept samples, throwing them away and starting over. Here is scenario I going after: your client asks you to build web application...
For some time now BlogEngine supports multiple commenting systems, from built-in to 3rd party, like Facebook or Disqus. Switching from one to another is as simple as selecting an option in the admin.