Blog Discussion: How to create your first Xperience by Kentico open-source contribution

Thanks for sharing this. This will be a good guide for any future contributions I make.

@benquinlan Welcome!

Don't think this post was in response to your awesome contribution 😅.

I had been meaning to write up some guidelines for the community for awhile and just recently got home from Connection in Prague. Some conversations there convinced me this should be a priority.

All that said, because you are part of the Kentico open-source community if you have any suggestions to help guide developers to success I'd love to hear them.

@seangwright I see that the article recommends prefixing extensions with XperienceCommunity. Going through what is already available on nuget.org, it looks like there are a number of KX13 projects already using that prefix.

Would it be worth updating the recommendation to use a prefix of XperienceCommunity.XbyK in order to provide an obvious separation between KX13 and XbyK extensions?

Good question, and one others have asked.

We want to plan for the future when KX13 won't be a concern for most Kentico customers, partners, and developers. At that point having the XbyK part will seem a little redudant since Xperience by Kentico will be the only active product.

So, today there is some awkwardness because both KX13 and XbyK integrations use the XperienceCommunity. prefix.

But, there are very few new KX13 integrations being created, most don't need to be updated (because there are no breaking changes with that product), and all "recently updated" XperienceCommunity projects are for Xperience by Kentico.

We have the same challenge with our packages - Kentico.Xperience.AspNetCore.WebApp is for KX13 but follows the same naming convention as Kentico.Xperience.WebApp which is for Xperience by Kentico.

In fact, we've actually taken the approach to add a KX13 moniker to our KX13 projects, like Kentico.Xperience.Algolia.KX13 instead of adding a special identifier to Xperience by Kentico libraries.

Thanks for creating this guide Sean - I like that you've created a form to submit new integrations too!

There's already an amazing list of open-source contributions, and I personally would love to see even more developers get involved. Not just by creating new packages, but also submitting ideas or code changes to help improve existing packages.

Not everyone has time to start brand new packages from scratch, but collaborating on existing projects is a great way for everyone to contribute!