Skip to content

Module Overview for Teachers

This page helps you find the right module for your lessons. It covers which modules exist, how they map to the curriculum and in what order they make sense.

How modules are structured

Every module in the Techlogia Lab consists of:

  • A topic (e.g. Linux basics, web servers, SSH security)
  • One or more lessons -- each lesson is a concrete scenario with its own VM
  • Several tasks per lesson -- checked automatically, with hints

Every module card in the Lab shows you:

Information Example
Title "First steps in the console"
Difficulty Beginner / Advanced / Expert
Estimated duration 30--60 minutes
Number of tasks e.g. 4 tasks

Available modules

Modules are added continuously

Techlogia publishes new modules regularly. The list below reflects the current state. New modules appear in the catalog automatically as soon as they are published.

Beginner modules

These modules require no prior knowledge and suit students from year 7 upwards.

Module Topic Tasks Duration Curriculum link
First steps in the console Getting to know the Linux terminal: files, directories, basic commands 4--6 approx. 30 min. Lower secondary computer science: operating systems, command line
HTML basics Building a simple web page with HTML 4--6 approx. 45 min. Lower secondary computer science: web development, markup languages

Advanced modules

These modules build on basic knowledge. Recommended from year 9 onwards or after completing the beginner modules.

Module Topic Tasks Duration Curriculum link
Deploying a web server with TLS Installing and configuring nginx and securing it with HTTPS 4--6 approx. 45 min. Upper secondary computer science: networks, encryption, client-server
SSH hardening Securing SSH access: keys, configuration, brute-force protection 4--6 approx. 45 min. Upper secondary computer science: IT security, authentication

Expert modules

For high-performing students, upper secondary level or vocational colleges.

Module Topic Tasks Duration Curriculum link
Further modules in preparation Containers, firewalls, monitoring -- -- IT security, network technology, systems administration

For a typical computer science course we recommend this sequence:

graph TD
    A["1. First steps in the console<br/>(Beginner)"] --> B["2. HTML basics<br/>(Beginner)"]
    B --> C["3. Web server with TLS<br/>(Advanced)"]
    A --> D["4. SSH hardening<br/>(Advanced)"]

Explanation:

  1. First steps in the console -- the mandatory foundation. Here students get to know the terminal they will need in every other module.
  2. HTML basics -- deepens working with files and gives a first web development context.
  3. Web server with TLS -- builds on the console knowledge and connects it to networking topics.
  4. SSH hardening -- can be done alongside or after the web server module. Thematically independent, but it does assume console experience.

Not every class has to work through every module

Choose the modules that fit your curriculum and time budget. With module visibility you can narrow the catalog for your class.

Time required per module

Plan for roughly this much time per module:

Difficulty Duration in the Lab Recommended lesson frame
Beginner 30--45 minutes 1 double period (introduction + Lab + review)
Advanced 45--60 minutes 1--2 double periods
Expert 60+ minutes 2 double periods, or as homework across several days

Individual differences

Fast students finish a beginner module in 20 minutes. Slower ones may need a second session the next day. The default of 3 sessions per student per day usually covers this.

Combining with homework

A proven approach when time is tight:

  1. In class: introduce the topic (15 min.), then start the module in the Lab.
  2. As homework: finish the remaining tasks before the next lesson.
  3. Next lesson: review the results using the class progress report.

School-exclusive vs. public modules

Type Visible to Characteristics
Public modules All learners (including self-learners without a school) Visible in the catalog as soon as an account exists
School-exclusive modules Only students in a class whose teacher has enabled the module Only visible in the catalog if the teacher activated it for the class

At present most modules are public. If Techlogia offers school-exclusive modules in future (e.g. curriculum-specific content for individual federal states), they will appear in your class catalog automatically, provided you have enabled them.

Feedback on missing topics

Missing a particular module? Write to info@techlogia.de with the topic and the target group. Teacher feedback feeds directly into how new modules are prioritised.

Using modules in class

Before the lesson

  1. Try the module yourself -- sign in as a teacher and start a session. That way you know the tasks and the likely stumbling blocks.
  2. Restrict module visibility -- hide modules that do not fit the current topic (see Modules & Quota).
  3. Prepare homework -- if you want to (see Homework).

During the lesson

  • Project the class code onto the whiteboard or projector.
  • Students sign in and start the module.
  • Use the Progress tab on the class detail page to see live who is where.
  • For active sessions: watch live (read-only) for students who are stuck.

After the lesson

  • Review the class progress -- who passed, who is stuck on which task?
  • Assign homework for unfinished modules if needed.
  • Discuss typical mistakes in the next lesson.

Frequently asked questions

"Can I create my own modules?"

Not at the moment. Modules are created and maintained by Techlogia (platform admins). If you are missing a specific topic, send a suggestion to info@techlogia.de.

"Are the modules tied to a specific curriculum?"

The modules are oriented towards typical computer science curricula for lower and upper secondary education. They are deliberately kept curriculum-independent so they can be used nationwide. The "curriculum link" column in the tables above gives a rough classification.

"Can I use only individual tasks from a module?"

Not directly. Teachers control visibility at module level, not at task level. You can, however, steer this organisationally (e.g. in the homework description: "Only solve tasks 1 and 2").

"Are there modules in other languages?"

All modules are bilingual (German and English). Students see the content in the language they have selected in the Lab.

"How often do new modules arrive?"

That depends on capacity and feedback. Techlogia works on new content continuously. If you would like to be notified when new modules appear, write to info@techlogia.de and ask to be added to the module notification list.

Further guides