How much of a brand-new subject can you actually defend teaching before the semester runs out?
Every field has been the new kid once. Computer science used to be one elective bolted onto a maths department before anyone trusted it with a building of its own. Psychology spent decades treated as a philosophy elective before it got to be a discipline in its own right. The pattern repeats itself: something genuinely new shows up, nobody has the appetite to build it a full degree overnight, and it gets squeezed into whatever space is politically available, usually one required course and one optional one, and told to prove itself.
That's an uncomfortable position for a subject to be born into. Too little room to actually cover it properly, and just enough visibility that if it goes badly, the whole idea of taking it seriously gets set back another five years.
The Argument Nobody Wins Cleanly
Picture a curriculum committee locked in a room for an afternoon, trying to agree on what a single required course can honestly promise to teach. One professor insists that if you cut the unglamorous technical fundamentals to make room for something flashier, you're not teaching the subject anymore; you're teaching a highlight reel.
"Nobody hires someone based on one impressive demo," she says.
Another disagrees just as firmly:
"If the first course isn't interesting, there won't be a second one worth building."
Neither of them is wrong, which is exactly the problem. A required course has to be rigorous enough to mean something and inviting enough that anyone actually finishes it. An elective, by contrast, gets to pick a single direction and go deep, but only if the required course beneath it actually did its job; otherwise, the elective spends half its time re-teaching material that should already be settled. Ask five different departments to solve this same puzzle and you'll get five different answers, none of them obviously correct, all of them defensible in the room where they were decided.
A Framework Worth Arguing With
There's a version of this problem that gets organized around a memorable shape, six ideas bundled under the name CANVAS. Taken one at a time, none of them are as settled as the neat acronym makes them sound.
Confidence first sounds unobjectionable until you ask what it actually costs. Building confidence early usually means starting simple, which is fine right up until "simple" becomes an excuse to avoid the genuinely hard material for another few weeks. Confidence built on easy wins isn't confidence, it's a delay.
Assess before assuming is the letter doing the least glamorous work and probably the most honest one. It just says: find out what's actually true before designing around a guess. The catch is that assessment takes time nobody budgeted for, and a committee under deadline pressure will happily skip it and assume anyway.
New tools as a means, not an end is the easiest letter to agree with in a meeting and the hardest to actually enforce once a syllabus gets written, because tools are simply easier to teach than judgment is. A tool has a manual. Judgment doesn't, which is exactly why it keeps losing the argument for class time.
Virtual environments, given real room is where the framework quietly contradicts its own first letter. Treating a genuinely complex subject seriously means diving in past the point where anyone feels confident, which is the opposite instinct from starting simple. CANVAS doesn't resolve that fight. It just makes sure both sides show up to have it.
Adaptable by design is less a teaching principle than an admission: nobody expects this to be right the first time, or the same twice. That's either refreshing honesty or a built-in excuse for never quite finishing the job, depending on who's asking.
Share it forward is the letter that only matters if someone actually does it, which is the quiet flaw in every version of this idea. A framework that isn't published, compared, or argued about by other departments just becomes one more binder on one more shelf. Sharing isn't a value you can teach into a curriculum. It's a habit an institution either has or doesn't.
Read that way, CANVAS isn't a solved formula so much as six separate pressure points a committee has to actually argue through, in order, rather than skip past because the acronym sounded complete.
One Version, Written Down
A Pedagogical Framework on Digital Arts built along these lines already exists inside the DIGARTED project: one core course and one elective course in digital art, designed for higher education institutions across Europe to adopt outright or adapt to their own programmes.
Nobody gets a whole new discipline right on the first try. The best anyone can do is write down which corners they cut, so the next person doesn't have to guess.
This work is part of the DIGARTED project, co-funded by the European Union under the Erasmus+ programme, supporting art educators and higher education institutions in building digital art capacity from the ground up.
If your own department has had to fight this exact argument out in a single afternoon, get in touch; we'd like to know which side won.