CO-API and CO-Data

Sunday, 02 August 2020 | Software Program

This is a rather late announcement but 'better late than never' I guess. Anyway, I have two 'new' software projects to announce. They are CO-API and CO-Data.

One of the coincidental points this announcement highlights is the relationship between these projects -- or, more precisely, there is one. CO-Data is a website which takes the meta-data from this (craigoates.net) site and displays it in a plethora of charts. For CO-Data to access that data, it uses CO-API to provide it. For the sake of clarity, CO-API is a RestAPI (website), which provides its users with the meta-data of craigoates.net.

Screenshot 1
Screenshot 1: The home page of CO-API
Screenshot 2
Screenshot 2: The home page of CO-Data
Screenshot 3
Screenshot 3: Artwork data charts on CO-Data

I think it's fair to say CO-Data is dependant on CO-API. Although, CO-API lacks the immediate visuals to demonstrate what it can do or its reason for existing. It's a software-developer-centric project. So, CO-API does benefit from CO-Data existing.

If you would like to see how CO-Data generates it's charts, you can visit its git repository and read the code there. CO-API has a 'preview' feature so you can see the JavaScript Object Notation (JSON) data it produces without writing a line of code.

As an aside, to reduce the C.P.U. load for the CO-Data website, I have utilised another project of mine: Skivvy. It's not essential for CO-Data to use Skivvy but it does help when running on (CO-Data) on low-end machines.

Relevant Links

Previous Back Next