Contentment v3.0.0-alpha001

Hey there Umbraco fans!

Quick note, as of Umbraco v9.0.0-rc002, the latest Contentment v3.0.0 alpha release is 3.0.0-alpha005.

With the release of Umbraco 9.0 Release Candidate, I am excited to announce Contentment v3.0.0-alpha! 🎉

For anyone following along, I had been documenting my developer journey for migrating from Umbraco 8 (.NET Framework 4.x) to Umbraco 9 (.NET Core 5). While there is much celebration around the active Umbraco Package Developers simply migrating their package code over to .NET 5, it is important for me to note the amount of human effort that goes in to these things. For Contentment, the initial migration took around 12 days work, with additional days (this week) to resolve any snags - a rough estimate is 100 hours development time for this release. I mostly say this for empathy reasons, if you hit any snags with the package, be friendly - and keep in mind that no one is intentionally breaking your website. Send praise to your favourite package developers, (okay okay, you know we're mostly talking about @KevinJump right? ❤️)

...and congrats to Umbraco HQ and everyone on the Unicore Team, particularly @bergmania - well done on reaching this v9 milestone! 🏅🎉

---

On with the show...

What's new?

Contentment v3.0.0-alpha003 has all the latest features as last week's v2.1.0 release.

Where can I get it?

With Umbraco 9, you can no longer install packages via the CMS backoffice, you must use NuGet.

For those using the NuGet Package Manager...

Install-Package Our.Umbraco.Community.Contentment -Version 3.0.0-alpha005

...or if you are using the dotnet command line interface?

dotnet add package Our.Umbraco.Community.Contentment --version 3.0.0-alpha005

Any changes?

The biggest change is with the configuration options. Rather than do this within a custom Composer class (on Umbraco 8), these are now done in the appsettings.json file.

Here are Contentment's configuration options, note within the "Umbraco" section:

"Umbraco": {
  "Contentment": {
    "DisableTree":  true,
    "DisableTelemetry": true
  }
}

If you prefer to use a strongly-typed configuration, you can do so in the Startup.cs ConfigureServices() method, like so...

public void ConfigureServices(IServiceCollection services)
{
	services
		.AddUmbraco(_env, _config)
		.AddBackOffice()
		.AddWebsite()
		.AddComposers()
		.AddContentment(
			settings: x => { x.DisableTree = true; x.DisableTelemetry = true; },
			listItems: x => { x.Exclude<Community.Contentment.DataEditors.CountriesDataListSource>(); })
		.Build();
}

Please note, the call to .AddContentment() is optional. If you aren't comfortable with the Startup code, don't worry, the Contentment package will still work as it does on Umbraco 8.

Bugs and snags

If you find any bugs or snags, do let me know. If it's a reproducible bug, then you can raise it on the issues, otherwise if it's more of a feature or suggestion, then starting a discussion is a better way to do that. Keep in mind that the usual contribution rules of engagement apply. 😃

Sponsorship

Only because I'm not promoting it as much as I could be... if my Umbraco packages are super helpful to you and/or your business, you can sponsor me on GitHub! ...and if monthly is too much, there is a one off sponsorship option!

Enjoy the release!

Cheers,
@leekelleher
✌️❤️🕊️