KI-Léierbud Inventory

Inventory of KI-Léierbud portal components:

1. PLESK Server
https://plesk06.vo.lu:8443/
Version: Obsidian 18.0.712
OS: AlmaLinux 96 x86-64

2. WORDPRESS CMS
https://admin.ki-leierbud.lu
Version: 6.8.2

3. KI-Léierbud Prototype
https://ki-leierbud.lu

4. KI-Léierbud Design Mockup
https://www.figma.com/design/1f98BTttNHQk5EU2vTYWAp/KI-LEIERBUD

5. KI-Léierbud Dot Icons Design
https://21st.dev/paceui/dot-loader/default

6. Backend API Server (Docker, JWT, OpenAI, NestJS)
IP: 85.93.210.120
https://github.com/ki-leierbud/api

7. Backend GPU Worker
LetzAI AI Models

8. Frontend Navigation + Mini-Applications (multilingual)
https://ki-leierbud.lu
https://ki-leierbud.lu/about.html
https://ki-leierbud.lu/contact.html
https://ki-leierbud.lu/faq.html
……

https://ki-leierbud.lu/knowledge/visionaries/
https://ki-leierbud.lu/knowledge/bits-bytes/
https://ki-leierbud.lu/knowledge/applications/
……

https://ki-leierbud.lu/quiz/real-ai/
https://ki-leierbud.lu/quiz/image-style/
https://ki-leierbud.lu/quiz/ai-timeline/
……

https://ki-leierbud.lu/polls/feelings/
https://ki-leierbud.lu/polls/opinions/
https://ki-leierbud.lu/polls/ai-in-schools/
……

https://ki-leierbud.lu/handson/my-first-image/
https://ki-leierbud.lu/handson/music-maker/
https://ki-leierbud.lu/handson/news-search/
……

It may be necessary to add subfolders within the different categories to manage difficulty levels.

9. Templates for mini-applications
For the knowledge, quiz, and polls categories, a total of about 7 different templates are needed:
* one for knowledge
* three for quiz
* three for polls
To customize a mini-application from a template, it is sufficient to specify the first WordPress article ID and, where applicable, parameters that cannot be managed through the REST API. Templates must be extended to support login when access to specific mini-applications is required.
For the HandsOn category, it is more difficult to use templates for mini-applications because of the variety of required functionalities. It is certainly possible to define sub-templates for certain tasks, but overall, the development of a custom mini-application should be considered for each HandsOn example.

I have added the code for several mini-applications to the GitHub repository, which can serve as examples and references for developing templates or custom mini-applications.

https://github.com/orgs/ki-leierbud/repositories (edited) 

More recent informations about the development of templates is provided in my contribution

admin.ki-leierbud.lu/archives/2107

10. Conference Room for Partner Meetings
made available by Visual Online
parking before the building
large screen with computer interface
free coffee and drinks offered

    Inventory of available KI-Léierbud project tools :

    a) DNS Server/Stock
    https://hosting.vo.lu/fr/domaines/domaines/

    b) Data Loss Protection
    Daily server backup copies

    c) Sentry Logs Checking
    https://sentry.io/welcome/

    d) Video Meetings Host
    https://meet.vo.lu/KIL

    e) Fiche descriptive KI-Léierbud

    https://ki-leierbud.lu/documents/KI-Leierbud-promo-4.pdf

    f) Messaging Service Slacks
    made available by LetzAI
    https://en.wikipedia.org/wiki/Slack_(software)
    https://slack.com/intl/fr-fr

    Inventory of Required Additional Components, Tools, and Tasks for the KI-Léierbud Project


    A) Mail Server (Component)
    To be set up shortly.


    B) VoIP Interface (Component)
    To be scheduled for the end of 2025.


    C) Documentation Center (Tool)
    Currently, project documentation for the development and management of KI-Léierbud is scattered across multiple locations:

    • In the private development section of the WordPress server: https://admin.ki-leierbud.lu/ (I suspect few, if any, have read these articles and links so far)
    • In individual emails and PDF documents
    • In the Slack messaging platform
    • In the KI-Léierbud GitHub account
    • In my personal GitHub account
    • On my personal website https://web3.lu/

    It is urgent to define a single, centralized documentation hub for the project. We must decide whether development-related information should be open-source or restricted, and then select the most appropriate hosting platform.
    To be set up shortly.


    D) Accounting Center (Tool)
    To my knowledge, we have not yet started a transparent accounting process for the costs and investments related to the KI-Léierbud project. Significant work has been done since the official start date, 1 July 2025.
    While it is clear that this information will not be open-source, we must provide it to the ministry. I recommend:

    • Listing all costs incurred to date
    • Sharing the data among partners
    • Hosting it on a protected platform so it can be reviewed by the ministry’s comité de suivi

    To be set up shortly.


    E) User Support Center (Task)

    • Provide user support via telephone, email, and chatbot

    To be in place for the portal launch in mid-October 2025.


    F) Content Management (Task)

    • Appoint authors, editors, translators, and other contributors to create content for the mini-applications

    To be defined shortly.


    G) Team Management (Task)

    • Assign team members responsible for managing the different components and tools, and for executing related tasks
    • Schedule regular video meetings with all responsible parties to track project progress
    • Produce written reports summarizing meeting results (possibly assisted by AI tools using meeting recordings)

    To start shortly.


    H) Statistics (Task)

    • Collect and process data to produce statistics for both internal and external distribution

    To be set up for the portal launch in mid-October 2025.