Add luuk1983.json to the samples folder

[Luuk1983]

I like to add myself to the list of participants. I have a repository where I will add multiple Umbraco code examples to. So when I have more examples, I can't just link to the entire repo as a whole, but rather to a subsection or folder. To me it made sense to link the url to the readme file directly (instead of using the readme property for that). But I'm not sure how this will be used and parsed in the future, so let me know if I should change anything!

[jemayn]

Hey @Luuk1983

I will leave the decision of what to link to to someone else, but I wanted to point out that the links in the readme that points to the actual files with code are not working atm.

[Luuk1983]

Hey @Luuk1983

I will leave the decision of what to link to to someone else, but I wanted to point out that the links in the readme that points to the actual files with code are not working atm.

Who doesn't love last minute folder structure changes without checking the links after the change.... They work now :)

[LottePitcher]

Hey @Luuk1983 - wonderful to hear that you're planning on building a selection of samples. I love the readme that you've started for this first 'custom conditions' example, and seeing that you intend to show a couple of ways to achieve the same results, and why you would recommend one way over the other. This is so useful!

In terms of how to submit the samples, I think for now we would appreciate the readme as the separate property, i.e.

    {
        "title": "Add custom condition to an existing backoffice extension",
        "description": "This sample demonstrates how to add a custom condition to an existing backoffice extension in Umbraco.",
        "url": "https://github.com/Luuk1983/UmbracoExamples/tree/main/ConditionsToExistingExtensions"
        "readme": "https://github.com/Luuk1983/UmbracoExamples/blob/main/ConditionsToExistingExtensions/README.md"
    }

We haven't got to writing the parsing code yet. but if we realise it would work better the other way we can change it! SuperTak!

[Luuk1983]

Hey @Luuk1983 - wonderful to hear that you're planning on building a selection of samples. I love the readme that you've started for this first 'custom conditions' example, and seeing that you intend to show a couple of ways to achieve the same results, and why you would recommend one way over the other. This is so useful!

In terms of how to submit the samples, I think for now we would appreciate the readme as the separate property, i.e.

    {
        "title": "Add custom condition to an existing backoffice extension",
        "description": "This sample demonstrates how to add a custom condition to an existing backoffice extension in Umbraco.",
        "url": "https://github.com/Luuk1983/UmbracoExamples/tree/main/ConditionsToExistingExtensions"
        "readme": "https://github.com/Luuk1983/UmbracoExamples/blob/main/ConditionsToExistingExtensions/README.md"
    }

We haven't got to writing the parsing code yet. but if we realise it would work better the other way we can change it! SuperTak!

@LottePitcher I updated the file to reflect your requested changes :)