Skip to content

Week 1

Assignments

Watch the video

Reflection: Managing and Uploading Multimedia Files on GitLab

Process

For this task, I explored how to upload and manage multimedia files such as images and videos on GitLab. I created visuals using Canva and produced videos using CapCut. After editing, I realised that some files were too large to upload directly, so I had to find ways to compress them before storing them in GitLab.

My process began with designing and exporting images in Canva, followed by recording and editing videos in CapCut. I then compressed both images and videos using the built-in export settings and, when needed, online compressors. Once the files were ready, I uploaded them to the appropriate folders in my GitLab repository — usually under docs/images or docs/learning-diary.

To make my documentation more complete, I added links and embedded media using Markdown syntax. For images, I used , and for videos, I used [video name] and (link).

Challenges and Solutions

One of the biggest challenges I faced was the file size limitation on GitLab. Many of my images and videos were initially too large to upload. I solved this by experimenting with compression methods — reducing image dimensions in Canva and exporting videos from CapCut at lower resolutions. I also discovered some free online compression tools that helped me reduce file sizes even further without losing too much quality. I tried to seek advices from Seh Yong and Steven @dfs Science Centre.

Another issue was linking videos and images correctly. At first, I encountered several “404 – not found” errors, which meant the links were broken. My videos could not be located! I was not sure why as the basic code seems to be correct. I have compressed according to the required resolution. Finally, I left it to the computer nerds at the back end as advised by Steven.

Key Learnings

This experience taught me that technical challenges are often part of the learning journey — especially when working with digital platforms. I learned how important it is to understand file management, organisation, and basic coding syntax like Markdown. I also became more comfortable using GitLab as a documentation and sharing platform, rather than just a storage space.

I realised that small habits, such as naming files clearly and maintaining folder consistency, make a big difference. The process also helped me appreciate the balance between creativity and technical constraints — a valuable lesson when guiding students through digital projects.

Application to My Teaching

This experience has many practical applications in my classroom. I can now guide students to document their work digitally using tools like Canva, CapCut, and GitLab(other simple digital platforms). This seems quite difficult because I am teaching in a primary school. They can create visuals, videos, and reflections that showcase their learning in an organised and professional way. I also can share this experience with my colleagues if it is not possible for the students.

More importantly, I can help them develop digital literacy, problem-solving, and persistence — the same skills I needed during this process. This connects strongly to the Makerspace movement, where students learn by doing, troubleshooting, and improving their creations.

Next Steps / Improvements

Moving forward, I would like to explore in linking larger videos through YouTube or Google Drive, embedding them instead of uploading directly.

Another goal is to deepen my understanding of Markdown formatting and explore how GitLab Pages can be used for further documentation in this project.

Tools and References

•   Tools used:

•   GitLab (for documentation and file organisation)

•   Canva (for image creation and compression)

•   CapCut (for video editing and compression)

•   Online compression tools

References and tutorials:

•   GitLab documentation on file uploads and Markdown

•   YouTube tutorials on CapCut video compression

•   Canva help articles on export and file resizing

Examples markdown

Code Example

Use the three backticks to separate code.

// the setup function runs once when you press reset or power the board
void setup() {
  // initialize digital pin LED_BUILTIN as an output.
  pinMode(LED_BUILTIN, OUTPUT);
}

// the loop function runs over and over again forever
void loop() {
  digitalWrite(LED_BUILTIN, HIGH);   // turn the LED on (HIGH is the voltage level)
  delay(1000);                       // wait for a second
  digitalWrite(LED_BUILTIN, LOW);    // turn the LED off by making the voltage LOW
  delay(1000);                       // wait for a second
}

sample photo

Video