If you haven't read the API thread,
please do so you have some idea of what I'm talking about!
After about a year break of developing anything MS related, I finished up the stormcaster API (as much as I wanted to, anyway), to the point where client apps could be built to consume the API. Simply put, stormcaster produces a RESTful API which allows client apps to request information such as rankings, online count, and send data to create users, login users, etc. By doing so, the frontend can be fully encapsulated from the backend logic.
This release is for a VueJS webapp, that consumes a stormcaster API. If you don't know what VueJS is, I recommend you skim through their website here.
The gist is that VueJS is a view library, that uses the idea of reuseable components to build single page applications. This is my first time using something like VueJS, so you may notice that this demo isn't super polished. Most noticeably, there is no application state retained between pages, which results in the webapp requesting API information over and over again, which isn't ideal. As I continue learning, this issue will be fixed.
Anyway, here's a live demo that you can use to register for an account, login, and view news/events/etc. See how quickly pages "feel" compared to regular websites. That's the future for ya! Note that this is primarly a technical demo
, the design can easily be
In the future, I will push an update that will allow the public to create administrator accounts (for demonstration purposes only). If you would like to play around with the source locally, I encourage you to download the source code at https://github.com/greenelfx/stormcaster-vue
. Note that you must first setup stormcaster API before using the VueJS app. Finally, I encourage you all to create other 3rd party clients for stormcaster. Since the API is platform agnostic, you can use anything from jQuery, to Angular, to C#.
(demo url: stormcaster-vue
(note that if nobody has visited the webapp in some time, Heroku will take some time to "spin up." This does not reflect on the performance of either stormcaster-api or stormcaster-vue)