Skip to content

The coding module

The coding module is the school-side view of the Coding, Robotics and AI pathway that learners work through in the student portal. Learners write code there; teachers set work, mark it and report on it here.

The pathway is CBC-aligned and runs Grade 1 to Grade 9. It covers block coding in the browser with nothing to install, robotics kits with project briefs and marking rubrics, and AI literacy, digital safety and problem solving. It comes with teacher training and lesson-by-lesson guides, and each level ends in a showcase where every learner has built something.

Go to Coding → Overview.

The school-wide coding overview

The coding overview summarises enrolment, activity and pathway progress.

Screen What it is for
Overview Participation and progress across the school
Classes Which classes are enrolled on the pathway, and where each has reached
Students Individual learners, their progress and their submissions
Assignments Coding tasks set to a class, with due dates
Projects Larger pieces of work, usually built in the Scratch sandbox
Quizzes Short knowledge checks
Exams Formal assessment, with per-exam analytics
Report cards Coding results in report form
Certificates Completion certificates for learners who finish a level

From Coding → Classes, enrol the class and choose the level of the pathway it starts at. Every learner in the class gets the pathway in their portal, and their progress starts reporting back here.

Classes enrolled in the coding pathway

Enrol at class level rather than learner by learner. Learners who join the class later pick the pathway up automatically.

Assignments and Projects are set to a class with a due date. Learners see the task in the portal, do the work — usually in Scratch — and submit from there.

Coding projects and submission status

Submissions arrive under the assignment. Each one can be opened, the learner’s project run, and a result recorded. Where the work is assessed by competency rather than a mark, it uses the same rubric mechanism as the rest of CBC.

Quizzes mark themselves and report immediately.

Coding exams are created and sat in the portal, and each has an analytics view showing the score distribution and which questions the class found hard. A question that almost everyone failed is usually a teaching signal rather than a cohort one.

Coding exams and their status

Robotics kits come with project briefs and marking rubrics, and are assessed here like any other project — a brief set to the class, work submitted, marked against the rubric.

Learners can program supported Arduino and Makeblock hardware from a Chromebook. In the student portal they open Coding → Playground, choose Arduino or Makeblock, and launch the official browser editor. Arduino opens Arduino Cloud Editor; Makeblock opens mBlock 5 Web. Each launcher includes the connection steps and a link to the vendor’s current supported-device guidance.

Two practical points schools learn the hard way:

  • Track the kits in Inventory, as assets with a custodian. Sets of small parts distributed to Grade 6 and never counted back in do not survive a term.
  • Book them. One set of kits and four classes needs a timetable, not goodwill.

Before moving a class to Chromebooks:

  1. Test the exact board or robot model on one Chromebook. Arduino supports a defined set of boards on ChromeOS, and mBlock support varies by device and connection method.
  2. Use data-capable USB cables. A charging-only cable powers the device but cannot upload a program.
  3. On managed Chromebooks, allow https://app.arduino.cc and https://ide.mblock.cc to request access under the Chrome Web Serial API policy.
  4. Keep only one mBlock editor tab open per Chromebook so it does not lock the serial port.

The pathway ships with teacher training and lesson-by-lesson guides, which matter more here than in other subjects — most schools are teaching this without a specialist.

The guides are in Lesson plans. A teacher one lesson ahead of the class is normal at the start and works fine, provided they have actually done the lesson first.

Each level ends in a showcase: every learner has built something and shows it.

It is worth treating as a real event — parents invited, work on screens, learners explaining what they made. It is the clearest evidence a school has that the pathway is doing anything, and it is far more convincing to a parent than a grade.

Set the date at the start of term so the projects are planned towards it.

Report cards produce the coding section of a learner’s report. Certificates shows the learners who have earned a Bronze, Silver, Gold or Platinum award for the selected term. Choose Print beside a learner to open their certificate as a PDF. The browser opens its print dialog; you can print a paper copy or choose Save as PDF.

Only earned certificates can be printed. If a learner is shown as Not yet, check the completion percentage and average mark on the same row, then finish or mark the missing work before trying again.

Coding report cards

Coding completion certificates

The learner Coding Playground now provides Chromebook-ready launchers for Arduino Cloud Editor and Makeblock mBlock 5 Web. This replaces the previous edit-only hardware code boxes: learners can now connect supported devices and upload from ChromeOS through the official editors.

Coding and Robotics award certificates can now be printed directly from Coding → Certificates. The print-ready certificate now uses the official ShuleOne Coding, Robotics & AI design, maps Bronze through Platinum awards to Tier One through Tier Four, and carries the learner, partner school, issue date, programme signatories, the official ShuleOne wordmark, and the school logo configured in Settings → School.