The main screen of WebWork Status. You’ll first notice that I screwed up the padding for the h3 that shows the status (ignore this, I’ll fix this soon).  After you notice how bad of a developer I am, you’ll see how the site basically works. You’ll s

WebWork Status

WebWork Status is a prototype project that allows anyone in my university to check the status of the WebWork servers (which are notorious for getting very slow before a major calc assignment is due).

After not being able to get ahead on my Calc work one night (another Calc had a WebWork assignment due), I made the first iteration of WebWork Status in 3 hours. Since then, I’ve continued to refine and update the website.

The website continued to run until May 2022 before I shut it down. Over summer 2021, the university upgraded the WebWork server so it never really went down.



Lines of code: ~500

Languages: HTML, JavaScript, Python

Frameworks: Materialize (based on Bootstrap 4), Flask

Timeframe: November 2020 - May 2022

This project is no longer running.

 The main screen of WebWork Status. You’ll first notice that I screwed up the padding for the h3 that shows the status (ignore this, I’ll fix this soon).  After you notice how bad of a developer I am, you’ll see how the site basically works. You’ll s

The main screen of WebWork Status. You’ll first notice that I screwed up the padding for the h3 that shows the status (ignore this, I’ll fix this soon).

After you notice how bad of a developer I am, you’ll see how the site basically works. You’ll see a status of webwork (which varies depending on the latest response time, same with the status dot). Then an approximate range of how long pages should take to load (+/- 5 seconds from the last response time with a bottom cap of 0).

Below that, information on the last response time measured (basically timing how long a requests request takes to the webwork site) is displayed. Right now, I’m playing with the idea of having the average response time for the last 30 minutes, but this needs some refinement.

And then there’s the last updated screen for knowing when everything was last updated.

 Of course, no site I make would be complete without a graph. The graph on WebWork Status shows a running log of the response times in the last 24 hours (blue line).  The red line shows the average 30-minute response times for each point on the graph

Of course, no site I make would be complete without a graph. The graph on WebWork Status shows a running log of the response times in the last 24 hours (blue line).

The red line shows the average 30-minute response times for each point on the graph. It is a rolling average (since line doesn’t start for a bit) on the left, but is right up with current data on the right).

In this screenshot, the line is cut off a bit - this was due to a WebWork outage on the day I took this screenshot. This is intentional behavior.

A pretty simple project to keep tabs on the status of WebWork!