WriteFreely VS Umbraco

Mastodon is a microblogging service, so not meant for large bodies of text. This is why the text entry box is small, the columns are somewhat narrow (especially in deck mode) etc.

Platforms like https://writefreely.org/ , which are designed to be for blogging and long-form writing, are the place to write this. Write Freely federates so one can follow accounts and interact with posts via Mastodon etc.

Write Freely, open source writing space

Docs - https://writefreely.org/

It's all about federation, in these federated networks all these servers talk to eachother and exchange messages about stuff going on on the servers. So it's easy to set up a hidden service for the webui of one of them, but it's sometimes quite obscure to try and set up the federation for one of them. It depends on what settings they honor and what other types of encryption and authentication they require and stuff. But, if you put some effort in ahead of time, you can make it really simple: I don't know how to do it in rust(lemmy is written in rust), but here's a neat example of how to do it in Go: https://github.com/writefreely/writefreely/pull/710 which requires no complicated configuration.

An alternative to Plume is WriteFreely, which is a pretty clean & simple experience. Just don't expect to much regarding customization.

I also wish write.as were more popular. It's like old Medium, but less popular but with a more reader-friendly business model and self-host-able (AGPL v3)

And since you've mentioned you want to write a blog, take a look at WriteFreely: https://writefreely.org/

Nowadays, especially for any Umbraco extensions I develop, I try to follow Umbraco's own namespaces as closely as possible. e.g. I'd put my custom IContentFinder classes under a [Brand].Web.Routing namespace. Mostly so that it feels logical for any other developers who may be familiar with Umbraco core code.

🔴 Umbraco-CMS: The simple, flexible, and friendly ASP.NET CMS used by more than 730.000 websites.

Umbraco

Umbraco - for .NET devs

I discovered that I could recreate the behaviour manually if I deleted the TEMP index files. For about 1 minute I got 0 results, but then it fixed itself. Using the debugger, I discovered the ExamineIndexRebuilder class and the RebuildOnStartupHandler. As it turns out, these are the key classes that handle index initialisation. There were a few changes that I had to make in order to get my integration tests to work:

As /u/transhumanist2000 said, the only other one I've seen that looked heavily supported and had a sizable following are dot net nuke, and I'd add, Umbraco (https://umbraco.com/). Unfortunately I haven't heard the best of feedback about these cmses.

I really like Umbraco (https://umbraco.com/), It has a decent community, and is on DotNetCore these days makes it very easy to use. You can setup most basic things yourself, but since it exists as a satellite to your site. You can integrate with it as deeply or not as you want. Plus the workflow for defining content is nice, the customer-facing UI is also slick, and adding custom elements to it and extending is easy too. Plus it's free.

This is an extension for Umbraco (version 9+) that lets you use your Umbraco content in a headless fashion. It is highly customizable, and you can tweak or replace every aspect of the generated output.

This week I became Umbraco HQ's Director of Developer Relations. We're not known for sensible job titles but I wanted to let you know that this call was, in fact, mine.

Note: While testing and writing this post I found an issue with nodes having a listview, so if that isn't really working as expected. See the issue here.