Training & Education Handbook

How we approached teaching informatics, programming, web technologies and e-government tools to different audiences: from basic skills to specialised topics.

This handbook is part of the Dianthos Web Engineering Handbook and reflects training practices used in real courses and one-to-one sessions from 2003 onwards.

← Back to the Web & IT Handbook overview

The role of training in web & IT projects

Training was treated as a central part of every project, not as an extra service. A system is truly delivered only when the people who use it understand what it does and how to operate it with confidence.

Over time, training covered:

  • Basic computer and internet skills for everyday users.
  • Web and social media usage for small businesses and professionals.
  • High-school exam preparation in programming.
  • University-level support in informatics and engineering subjects.
  • Programming languages and core CS topics.
  • E-government tools, digital signatures and online public services.

The common objective was practical autonomy: learners should be able to continue without constant external help.

Defining audiences, goals & prerequisites

Effective training starts with clarity about who is learning and why. The same topic must be taught differently to a business owner, a high-school student and a university engineer.

Key questions before designing a course

  • What problem is this training supposed to solve for the learner?
  • What prior knowledge can we realistically assume?
  • Which skills or outcomes must be visible at the end of the course?
  • How much time and attention can learners invest per week?

Answering these questions prevented over-ambitious programmes and helped focus on essentials instead of on long lists of topics.

Basic informatics & everyday digital skills

Many learners did not need to become programmers. They needed to feel safe and competent using computers, the web and common applications.

Typical topics in basic training

  • Operating system basics and simple maintenance.
  • Using browsers, tabs, downloads and safe navigation.
  • Email: accounts, attachments, basic organisation and hygiene.
  • Office tools: word processing, spreadsheets and presentations.
  • Backups and basic protection against viruses and scams.

Sessions were strongly hands-on: learners worked on their own machines whenever possible, performing tasks they actually needed in their daily life or work.

Internet & social media for individuals and businesses

As the web matured, training increasingly focused on how to use online presence and social platforms responsibly and productively.

Focus areas

  • Understanding how websites, browsers and search engines interact.
  • Creating and managing accounts on major platforms.
  • Privacy, security and digital footprint considerations.
  • Using social media for professional visibility and basic promotion.
  • Recognising misinformation, scams and social engineering attempts.

For small businesses, examples were taken directly from their own sites and profiles, turning training into immediate improvements.

High-school exam preparation in programming

A recurring area of work was preparation for final-year high-school exams in programming and algorithmic thinking. The goal was not only success in exams but also a solid foundation for future studies.

Typical elements

  • Review of core algorithmic concepts and notation used in the syllabus.
  • Systematic practice with representative exam-style exercises.
  • Step-by-step construction of solutions: from problem statement to algorithm and code.
  • Common error patterns and how to avoid them under time pressure.
  • Strategies for managing time and checking work during the exam.

Emphasis was placed on understanding rather than memorising specific solutions.

University-level support & advanced topics

For university students in informatics and engineering, training often took the form of targeted support around challenging subjects or projects.

Examples of topics covered

  • Data structures and algorithms.
  • Programming in C, C++, Java, Pascal, MATLAB and related tools.
  • SQL and database fundamentals for applications.
  • Theory of computation topics: automata, complexity at an introductory level.
  • Game theory and scientific computing at a practical, example-driven level.

Work typically alternated between concept explanations, solving exercise sets and reviewing parts of student projects or assignments.

Programming, web & e-government applications

Beyond academic topics, many sessions focused on concrete technologies used in projects and in public-sector workflows.

Programming & web technologies

  • HTML & CSS fundamentals for building and understanding web pages.
  • Introduction to PHP, JavaScript and typical LAMP-style environments.
  • CMS usage: managing content, menus and modules in systems such as Joomla.

E-government and digital signatures

  • Obtaining and managing digital certificates and signatures.
  • Secure document exchange and basic encryption concepts.
  • Using online portals for public tenders and administrative processes.
  • Practical workflows for submitting and tracking electronic applications.

Training in these areas was usually delivered around real tasks the organisation needed to complete, not generic demonstrations.

Course design, materials & delivery formats

Courses varied from one-to-one sessions to small groups, from short intensives to longer programmes. Regardless of format, a few design choices were consistent.

Course structure

  • Clear outline of modules and estimated time per module.
  • Alternation between explanation, demonstration and practice.
  • Short summaries at the end of each session, with “next steps”.
  • Room for questions and review of real problems brought by learners.

Materials

  • Concise notes or checklists instead of very long manuals.
  • Annotated examples of code, screenshots or step-by-step procedures.
  • Exercise sets with increasing difficulty and reference solutions.
  • Links to selected external resources for deeper study.

Delivery formats included in-person sessions, remote support and blended approaches depending on context and tools available.

Assessment, feedback & follow-up

Assessment was used to guide learning rather than to create pressure. Small, frequent checks of understanding often worked better than large final tests.

Assessment practices

  • Short quizzes or exercises at the end of topics.
  • Review of homework or project fragments, with specific comments.
  • Occasional timed exercises for exam-oriented courses.
  • Simple rubrics or criteria so learners knew what was considered “good enough”.

Feedback & follow-up

  • Encouraging learners to articulate what they found difficult.
  • Adjusting pace and depth based on observed progress.
  • Providing brief follow-up notes or summaries after key sessions.
  • Suggesting personalised next steps once a course ended.

The long-term goal was to make learners independent in seeking and evaluating new information as technologies evolved.