Translating from GitHub to Website

Hello everybody! I've been on Spring Break this week, so I haven't gone to work at the office this week. However, as suggested by Zachary Ginsberg last time, I'll show you with some pictures how the GitHub code goes into the LoopLogic API site, as well as how the interface can affect user experience!

First of all, here is a quick screenshot of what it looks like on the GitHub page of codes:

Not much huh? But you have to understand, these are like how your computer organizes documents. There are folders within these with even more files, and each file contains a bunch of complicated code. When we link a website domain to the GitHub page, GitHub will then take the code within these folders and then run them. So all the code that is within here....

....becomes this! Pretty neat huh?

Now, in my last post, I talked about how important user interface is right? Well, above is a good example: colors. Each of the interactable subsection is color coded in a way that pops out and grabs the user's attention. With some nifty code, we were able to do the same thing as well within the subsection!

See how vibrant the page is? It will hopefully make it a lot easier for the user to get comfortable with how to navigate around the API toolkit. This will boost the likelihood that the user then becomes a consumer, which is the ultimate goal of having a good interface.

Well, till next time!