Canvas Automation

Background

Canvas, like many niche-market systems, is general purpose enough, and configurable enough, to achieve the goals of most individuals, most of the time. But that often means that certain actions and certain opportunities get missed, because they don’t fit in the frameworks that fit with the design philosophy. Does that make the design wrong? Not at all. Designing software is a constant game of push-pull, with some features pushing the design in specific ways. That push sometimes pulls other features as well, which can mean desired features have to change to meet requirements elsewhere or that some features get pulled straight into the woodchipper.

Thankfully, the fine folks who built Canvas offer ways to develop your own integrations and your own supplemental systems, and hence this project. Our goal: create some features that facilitate our specific course and section workloads, and maybe build a project that can be used to demonstrate some software engineering skills to students in the process.

Resources

The project is on GitHub, but contributors are currently restricted to students in one of my courses. However, if you are interested in adding specific features, please reach out and we can have a discussion. If you want to see what we have in the queue, check out the issue list on GitHub.

Communication

Below are the most recent blog posts that likely reference this project. Updates are likely always going to have a supporting post, and this is the best way to see the history of work and most recent “official” status.

Playing with Diagrams

One thing I’ve found out about myself is that I don’t care much for many of the diagramming tools out there. Some of it is lack of seat time, as the mechanisms for building things like use case diagrams and…

Doing some Dev Work

One of the things I have decided after a year of this whole teaching gig is that if I don’t make time to keep my skills sharp, I will rapidly lose track of what it’s like to be a professional.…