This repository covers the integration between our Skybrud.Integrations.BorgerDk package and Umbraco. This gives editors the option to insert Borger.dk articles as part of their content in their own pages in Umbraco.

The v4/main branch (the one you're viewing now) contains the Umbraco 9 implementation, while an older implementations for Umbraco 8, Umbraco 7 and Umbraco 6 can be found in the v3/main, v2/main and v1/main branches respectively.

• Installation
• Setup
  • In the grid
  • As a property
• Municipalities

1. NuGet Package
   Install this NuGet package in your Visual Studio project. Makes updating easy.

2. ZIP file
   Manually unzip and move files to the root directory of your website.

This package comes with the option to insert an article as a control in the Umbraco Grid. The control however needs a bit of configuration, so you have to add the editor manually.

The editor requires you to specify the municipality to be used, since each munipality has the option for adding specific content to a given article. If you don't know the municipality ID, you can find it in this list. 630 as shown in the examples below is Vejle Kommune.

If you wish to add the editor in a custom package.manifest file, it could look like this:

{
    "gridEditors": [
        {
            "name": "Borger.dk",
            "alias": "skybrud.borgerdk",
            "view": "/App_Plugins/Skybrud.BorgerDk/Views/BorgerDkGridEditor.html",
            "icon": "icon-school",
            "config": { 
                "municipality": 630
            }
        }
    ]
}

You can also just add the editor to the global configuration file located at ~/config/grid.editors.config.js. In that case you could just append the JSON for the editor to the array of editors:

{
    "name": "Borger.dk",
    "alias": "skybrud.borgerdk",
    "view": "/App_Plugins/Skybrud.BorgerDk/Views/BorgerDkGridEditor.html",
    "icon": "icon-school",
    "config": { 
        "municipality": 630
    }
}

If using our Skybrud.Umbraco.GridData-package for showing the grid on your website, you can use the BorgerDkGridControlValue class (which inherits from BorgerDkArticleSelection used in the property editor) for the value of the Borger.dk grid control.

In order for the grid package to return a strongly typed model, you should use the default skybrud.borgerdk editor alias as shown in the JSON examples above, or specify a custom alias either ending with .borgerdk or containing .borgerdk. - eg. mysite.borgerdk or mysite.borgerdk.main. If you use another editor alias, you should add your own grid converter to handle the model.

If you're using our grid package, and already have a reference to the control holding the Borger.dk article, you can access the value shown in the Razor partial view example below (where Model is the control):

@using Skybrud.Umbraco.BorgerDk.Grid.Values
@using Skybrud.Umbraco.BorgerDk.Models.Cached
@inherits UmbracoViewPage<Skybrud.Umbraco.GridData.GridControl>
              
@{

    BorgerDkGridControlValue value = Model.GetValue<BorgerDkGridControlValue>();

    if (!value.HasSelection || !value.Article.Exists) { return; }

    foreach (BorgerDkCachedMicroArticle microArticle in value.MicroArticles) {
        <div class="BorgerDkMicroArticle">
            <h2>@microArticle.Title</h2>
            @Html.Raw(microArticle.Content)
        </div>
    }

    foreach (BorgerDkCachedTextElement block in value.Blocks) {
        <div class="BorgerDkText">
            <h3>@block.Title</h3>
            @Html.Raw(block.Content)
        </div>
    }

}

The value.HasSelection property indicates whether the value has an article selection. It is necessary to check this since an editor might insert the Borger.dk grid control on a page, and then save the page without actually selecting an article, leaving the selection empty.

The value.Article property is a reference to the cached article. When fetching an article from the Borger.dk webservice through Umbraco, it will automatically be saved/cached on the disk for later use. The value.Article.Exists then indicates whether the article is actually saved on the disk. If not, the example just returns since we don't have any content to show.

Also in the example, the properties value.MicroArticles and value.Blocks will only contain the micro articles and text elements that the editor has selected in Umbraco, while all micro articles and text elements of the article can be accessed through value.Article.MicroArticles and value.Article.Blocks.

This will be supported in the future ;)