Skills You Need

White Label Data is a low-code platform that takes care of a lot of the hard stuff, but you still have some work to do. Here are the basic skills you need to have to create your data application using White Label Data.

Know how to edit text files

Choose your favorite text editor such as Sublime, Atom, Vim, or any other editor that you are comforable with. We authorized our demo using Sublime.

A basic understanding of Git

You’ll most likely be using a GitHub repository to store and version control your project files. If you are not a fan of command line tools, try using Github Desktop for MacOS and Windows.

The ability to write SQL

If you came across this site, you are probably interested in creating a data application and know a thing or two about querying a database. White Label Data requires you to formulate SQL queries to get data from your database. If you are just getting started with SQL, you can find examples here.

A willingness to edit JSON

We store configuration in JSON format. There are other options out there (YAML, TOML, etc.), but we standardized on JSON because of its ability to cross over between human-editable and machine-editale. You won’t have to write JSON from scratch. We provide templates and examples. For example, here is how you add pages to the navigation (more on this later):

"app_pages": [
                    "page_type": "html",
                    "nav_category" : "Sightings",
                    "page_name": "overview",
                    "page_title": "Overview",
                    "page_src" : "overview.html",
                    "cache_hours" : 1
                    "page_type": "html",
                    "nav_category" : "State Info",
                    "page_name": "bystate",
                    "page_title": "By State",
                    "page_src" : "bystate.html",
                    "cache_hours" : 1

Some basic HTML skills

Don’t be scared off by this last one. We mean really basic. Here is an example of HTML from our Bigfoot Demo that renders some tabs with a visualization on each tab:

  <card height=620 cols=12>

And the result looks like this in the app:


Note that the contents of the visualizations are configured in separate files and specified in SQL AND JSON.