Can students hand in more than one file?

If you allow it. You set how many and how large, up to twenty files and twenty megabytes.

Where does the work go?

Into the platform, against that student and that task, where you and they can both see it. It never becomes an email attachment.

Can I collect work from a class without setting a coding task?

Yes. A written task exists for exactly that.

Can an assignment be a deployed web app rather than a file?

Yes. Choose A deployed app under What to hand in and which of Python, Node, Go, Java and static HTML, CSS and JavaScript sites it should be, and the student deploys it from GitHub and hands the deployment in.

Written assignments and hand-ins

Not everything is code. A written task is a brief the whole class reads, and what they hand in against it is whatever you decide to accept: a PDF, a document, images, or a set of files.

Write the brief once

A written task is one thing the class reads rather than a copy each, so correcting a typo in the brief corrects it for everybody. It takes headings, lists and code in the same way an exercise’s instructions do.

The What to hand in setting on a written task: which kind of file, how many and how big — What may be handed in, set on the task: a PDF under 2 MB unless you say otherwise.

Say what may be handed in

Per task: what kind of file, how many, and how big. The default is one PDF under two megabytes, which is right for a typed report and deliberately short of a scan of one.

The student sees the rule before they choose a file, and the wrong sort is refused with a sentence rather than accepted and lost.

An assignment has no Save button: the brief and the hand-in rule save themselves a second after your last change, and a line in the header says what became of it. Ctrl+S still saves at once. The save waits while the hand-in form is half answered, for example a deployed app with no kind chosen yet, and the page says what is missing. A rule is only sent when you changed it, so a second tab left open does not put a task set to take anything back to one PDF. The most you can ask for is twenty files and twenty megabytes, and a rule the platform refuses is said in the header in place of Saved.

See who has read it

A written task records who has opened it and when. That is the only progress a task made of words has, and it stands where a program’s tests stand on every list of tasks. A quiz shows its best score there instead.

Or ask for a deployed app instead of a file

One of the choices under What to hand in is A deployed app, with a second dropdown for which language. The student’s task page then links them to the deploy page with that language chosen; they deploy, check it works and press Hand it in, and what is handed in is the repository, the branch and the two commands their app ran with.

Whoever marks it presses Deploy app on the submission and the same app comes up again, without spending their own daily allowance of app time.

Marking it closes it

A hand-in stays open until you mark it. Marking closes it; sending it back opens it again and tells them why. A due date shows Overdue and refuses nothing unless you tick “Stop taking work after that date” beside it: then a hand-in after the end of that day in London is refused, though saving never is and a quiz is never shut that way.

Questions people ask

Can students hand in more than one file?: If you allow it. You set how many and how large, up to twenty files and twenty megabytes.
Where does the work go?: Into the platform, against that student and that task, where you and they can both see it. It never becomes an email attachment.
Can I collect work from a class without setting a coding task?: Yes. A written task exists for exactly that.
Can an assignment be a deployed web app rather than a file?: Yes. Choose A deployed app under What to hand in and which of Python, Node, Go, Java and static HTML, CSS and JavaScript sites it should be, and the student deploys it from GitHub and hands the deployment in.