GitHub Sync Test Course

This repository is a test course for the moodle-local_githubsync Moodle plugin. It demonstrates the expected repository structure and serves as a reference for course developers building content that syncs from GitHub into Moodle.

How It Works

The GitHub Sync plugin lets you author Moodle course content as HTML files in a GitHub repository. The repository becomes the single source of truth — content is synced into Moodle automatically, and any direct edits made in Moodle will be overwritten on the next sync.

Syncing can happen four ways:

• Manual sync from the course's GitHub Sync settings page in Moodle
• Scheduled task (hourly cron) for courses with auto-sync enabled
• Webhook triggered instantly on every git push
• CLI for bulk or per-course syncing

The plugin uses content hashing to detect changes — only modified files are updated on each sync. Files removed from the repo are automatically hidden (not deleted) in the course.

Repository Structure

course.yaml                              # Course-level metadata
assets/
  css/
    custom.css                           # Custom stylesheets
  images/
    placeholder.png                      # Image assets
  js/                                    # JavaScript files (if needed)
sections/
  01-introduction/
    section.yaml                         # Section metadata
    01-welcome.html                      # Page activity (default)
    02-course-handbook/                  # Book activity (directory)
      book.yaml                          # Book metadata
      01-getting-started.html            # Chapter 1
      02-assessment-guide.html           # Chapter 2
      03-key-resources.html              # Chapter 3
      04-library-access.html             # Chapter 4
    02-course-overview.html              # Page activity
    03-notice.html                       # Label activity (via front matter)
  02-module-one/
    section.yaml
    01-lesson-one.html                   # Page activity
    02-safety-training/                  # Lesson activity (directory)
      lesson.yaml                        # Lesson metadata
      01-introduction.html               # Content page
      02-safety-rules.html               # Content page
      03-quiz-tf.html                    # True/false question
      04-quiz-mc.html                    # Multichoice question
      05-review.html                     # Content page
    03-summary.html                      # Page activity
    04-external-resource.html            # URL activity (via front matter)

Naming Conventions

• Sections live inside sections/ and use the pattern NN-name/ (e.g., 01-introduction, 02-module-one)
• Activities within each section use the pattern NN-name.html (e.g., 01-welcome.html, 02-course-overview.html)
• Numeric prefixes control the display order and are stripped from the name shown in Moodle — 02-course-overview.html becomes "Course Overview"
• Gaps in numbering are fine (e.g., 01, 03, 04 with no 02)

Developing a Course

Step 1: Create the Course Configuration

Create a course.yaml in the repository root with course metadata:

fullname: "My Course Title"
shortname: "MYCOURSE01"
summary: "A brief description of the course."
format: topics
visible: true

Field	Description
fullname	The full course name displayed in Moodle
shortname	A unique short identifier for the course
summary	HTML or plain text course description
format	Moodle course format (topics, weeks, etc.)
visible	true or false — whether the course is visible

All fields are optional. If course.yaml is omitted, course metadata is not modified during sync.

Step 2: Create Sections

Create numbered directories inside sections/. Each directory becomes a Moodle course section (topic).

sections/
  01-getting-started/
  02-core-concepts/
  03-advanced-topics/

Optionally add a section.yaml inside each section directory:

title: "Getting Started"
summary: "<p>This section covers the basics you need to know.</p>"
visible: true

If no section.yaml is present, the section title is derived from the directory name (numeric prefix stripped, hyphens replaced with spaces, title-cased).

Step 3: Create Activities

Add .html files inside each section directory. Each file becomes a Moodle activity.

Page Activities (default)

Any .html file without front matter (or with type: page) becomes a Page activity — a full content page students click into to read.

<h2>Welcome to the Course</h2>
<p>This is your first lesson. Content supports standard HTML including Bootstrap classes.</p>
<div class="alert alert-info">
  <strong>Tip:</strong> You can use Bootstrap components in your content.
</div>

Label Activities

Labels display content directly on the course page without requiring a click-through. Add type: label in YAML front matter:

---
type: label
---
<div class="alert alert-warning">
  <strong>Important:</strong> Complete the previous section before continuing.
</div>

URL Activities

URL activities link to an external resource. Add type: url and a url field in front matter:

---
type: url
name: "Moodle Documentation"
url: "https://docs.moodle.org"
---
<p>Visit the official Moodle documentation for more information.</p>

Book Activities

A subdirectory inside a section that contains a book.yaml (or any subdirectory without a lesson.yaml) becomes a Book activity. Each .html file in the directory becomes a chapter, ordered by numeric prefix.

sections/
  01-introduction/
    02-course-handbook/
      book.yaml
      01-getting-started.html
      02-assessment-guide.html

book.yaml sets book-level metadata:

title: "Course Handbook"
numbering: numbers
intro: "<p>Essential information for students.</p>"

Field	Description	Default
title	Override the book name	Derived from directory name
numbering	Chapter numbering: none, numbers, bullets, indented	numbers
intro	HTML description on the book's intro page	Empty

Chapter files support front matter for per-chapter settings:

---
title: "Getting Started Guide"
subchapter: true
---
<h2>Welcome</h2>
<p>This chapter covers...</p>

Field	Description	Default
title	Override the chapter title	Derived from filename
subchapter	true to indent under the previous chapter	false

Lesson Activities

A subdirectory inside a section that contains a lesson.yaml becomes a Lesson activity. Each .html file becomes a lesson page — either a content page, a true/false question, or a multichoice question, controlled by front matter.

sections/
  02-module-one/
    02-safety-training/
      lesson.yaml
      01-introduction.html
      02-safety-rules.html
      03-quiz-tf.html
      04-quiz-mc.html
      05-review.html

lesson.yaml sets lesson-level metadata:

title: "Safety Training"
intro: "<p>Complete this lesson on workplace safety.</p>"
practice: true
retake: true
feedback: true
review: false
maxattempts: 3
progressbar: true

Field	Description	Default
title	Override the lesson name	Derived from directory name
intro	HTML description on the lesson intro page	Empty
practice	Practice lesson — no grades recorded	false
retake	Allow students to retake the lesson	true
feedback	Show feedback after answering	true
review	Allow students to review their answers	false
maxattempts	Maximum number of attempts	1
progressbar	Show progress bar	true

Content pages (default — no type in front matter):

---
title: "Introduction to Safety"
---
<h2>Welcome to Safety Training</h2>
<p>In this lesson you will learn about workplace safety.</p>

A "Continue" button is automatically added. The last page links to End of Lesson.

True/false questions — set type: truefalse:

---
type: truefalse
title: "PPE Requirement Check"
correct: true
feedback_correct: "Correct! PPE must always be worn in designated areas."
feedback_incorrect: "Actually, PPE IS required at all times in designated work areas."
---
<p>Personal protective equipment (PPE) must be worn at all times in designated work areas.</p>

Field	Description
correct	true or false — which answer is correct
feedback_correct	Feedback when the student answers correctly
feedback_incorrect	Feedback when the student answers incorrectly

Multichoice questions — set type: multichoice:

---
type: multichoice
title: "Emergency Procedure"
answers:
  - text: "Call your supervisor and evacuate"
    correct: true
    feedback: "Correct! Always alert your supervisor and evacuate safely."
  - text: "Try to fix it yourself"
    feedback: "No, never try to handle an emergency alone without proper training."
  - text: "Ignore it and continue working"
    feedback: "Never ignore an emergency situation - safety comes first."
---
<p>What should you do if you discover a fire in the workplace?</p>

Each answer has text, an optional correct: true flag (omit or set false for wrong answers), and feedback. Correct answers advance to the next page; incorrect answers stay on the current page.

Front Matter Reference

Front matter is optional YAML at the top of any .html file, delimited by --- markers.

Section-level activities (files directly in a section directory):

Field	Description	Default
type	Activity type: page, label, or url	page
name	Override the activity name	Derived from filename
url	External URL (required when type: url)	—
visible	Show or hide the activity (true/false)	true

Lesson pages (files inside a lesson directory):

Field	Description	Default
type	Page type: content (default), truefalse, multichoice	content
title	Override the page title	Derived from filename
correct	Correct answer for true/false (true/false)	true
feedback_correct	Feedback for correct answer	Empty
feedback_incorrect	Feedback for incorrect answer	Empty
answers	List of answer options for multichoice	—

Step 4: Add Assets

Place static assets in the assets/ directory. The directory structure is preserved when uploaded to Moodle's file storage.

assets/
  css/
    custom.css
  images/
    diagram.png
    photo.jpg
  js/
    interactive.js

Allowed File Types

Category	Extensions
Stylesheets	.css
Scripts	.js
Images	.png, .jpg, .jpeg, .gif, .webp, .ico, .bmp
Fonts	.woff, .woff2, .ttf, .eot, .otf
Media	.pdf, .mp3, .mp4, .webm, .ogg
Data	.json, .txt, .csv, .xml

Note: .svg and .php files are blocked for security reasons.

Referencing Assets in Content

Reference assets using relative paths from the repository root. The plugin automatically rewrites these to Moodle pluginfile.php URLs during sync.

<link rel="stylesheet" href="assets/css/custom.css">
<img src="assets/images/diagram.png" alt="Architecture diagram" width="400">

Both assets/... and ../assets/... path formats are supported.

Step 5: Connect to Moodle

1. In Moodle, navigate to the target course and open GitHub Sync in the course settings
2. Enter the Repository URL (e.g., https://github.com/your-org/your-course-repo)
3. Enter a GitHub Personal Access Token with repo scope (or public_repo for public repos)
4. Set the Branch (defaults to main)
5. Optionally enable Auto-sync for hourly automatic updates
6. Click Sync from GitHub to perform the initial sync

Step 6: Set Up Webhooks (Optional)

For instant sync on every push:

1. In your GitHub repo, go to Settings > Webhooks > Add webhook
2. Set the Payload URL to https://your-moodle-site.com/local/githubsync/webhook.php
3. Set Content type to application/json
4. Enter the webhook secret (must match the Moodle admin setting)
5. Select Just the push event

Content Authoring Tips

• Write HTML fragments, not full documents — no <html>, <head>, or <body> tags needed
• Bootstrap 5 classes are available since Moodle uses Bootstrap (e.g., alert, card, badge)
• All HTML content is sanitized by Moodle's HTMLPurifier — <script> tags and event handlers will be stripped
• Use semantic HTML for accessibility (<h2>, <h3>, <ul>, <table>, etc.)
• Content removed from the repo is hidden in Moodle, not deleted — this preserves student activity data
• Keep YAML configuration simple — the plugin's parser supports basic key: value pairs, quoted strings, and booleans

Example Workflow

1.  Clone the course repository
2.  Create or edit HTML files in sections/
3.  Add any images, CSS, or other assets to assets/
4.  Commit and push to the configured branch
5.  The plugin syncs changes into Moodle (via webhook, cron, or manual trigger)
6.  Review the course in Moodle to verify