Custom widget consists mainly of two types of files: the custom widget JSON file (explained in more detail in previous blog) and the resource files.
The custom widget JSON file contains the metadata of a custom widget. It defines all the ingredients of a custom widget and references its resource files by their URLs.
The resource files are all the files of the custom widget that make it work properly, for example, JavaScript files, CSS files, HTML files, image files, and more.
To host a custom widget, you need two locations on which these files are distributed:
In this blog I will show you how you can host your Custom Widgets into the GitHub.
Before you start uploading your Custom Widgets into the GitHub, you must first create an account in case if you don't have one.
GitHub Pages is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on GitHub, optionally runs the files through a build process, and publishes a website.
We will use this feature that GitHub is offering to host our Custom Widget's resource files.
Below you will find a Demo where I highlighted the different steps that you need to know for hosting your Custom Widget into the GitHub:
You can visit the GitHub Docs in order to know more about Pages, naming, the different type of repositories and Custom domains.
Please consult the GitHub Pages documentation on their Usage limits before implementation/going to production.
You can visit as well our new GitHub repository where you can find several Custom Widget Samples ready to use.
If you are interested in other hosting options, I invite you to read my blog: how to host your Custom Widgets into the SAP BTP
See you soon for new blogs !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
8 | |
7 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
5 |