I'd suggest reaching out to the owners of the github repositories you are referencing.
The first, 'contentment' has a release status note that says:
Release status:
My aim to have a private v1.0 beta release ready soon,
with a public release by end of Q1 (March) 2020.
So this indicates the author is not ready to release the project as an Umbraco package 'yet'. It would be a risk to use this as is in a production site - but you could perhaps ask the author, whether they would provide you with the v1.0 beta release.
WIthout a release of either version as an official Umbraco package then again worth getting in touch with all involved to see what will be supported and released moving forwards.
From a technical point of view, generally speaking - if you pull a project and build this will produce a dll to put in the bin folder of your site, but you'll also need to copy in any supporting app_plugins files if the package
requires/ships with them, eg .js, .css, package.manifest and .html files - some packages may also require configuration in appsettings in Web.config
The steps to turn third party source code in to a package.
Hey guys this is the source code for two packages for Umbraco - But they have not been made in to packages.
https://github.com/leekelleher/umbraco-contentment
https://github.com/bielu/nuPickers/tree/v8/develop
How do I turn this code in to a package I can install on my umbraco website?
Hi Ayo
I'd suggest reaching out to the owners of the github repositories you are referencing.
The first, 'contentment' has a release status note that says:
So this indicates the author is not ready to release the project as an Umbraco package 'yet'. It would be a risk to use this as is in a production site - but you could perhaps ask the author, whether they would provide you with the v1.0 beta release.
The second repo, is a fork of nuPickers the V7 package - the orginal authors are building a v8 version here: https://github.com/uComponents/Pikachu/issues
WIthout a release of either version as an official Umbraco package then again worth getting in touch with all involved to see what will be supported and released moving forwards.
From a technical point of view, generally speaking - if you pull a project and build this will produce a dll to put in the bin folder of your site, but you'll also need to copy in any supporting app_plugins files if the package requires/ships with them, eg .js, .css, package.manifest and .html files - some packages may also require configuration in appsettings in Web.config
regards
Marc
is working on a reply...