• 
  line break for lists
• SidebarNav Header change to Thilo Online for now
• Exchange "Erste Hilfe with negative one"

Let's meet in January and fix the search field to query the data that comes from the json files that we get from the server.

Containerize the whole Thilo Tech Stack, so it can be easily instantiated.

• Containerize the frontend (build with GitHub Action and host it on GitHub Container Repo)
• Create docker compose with all components (database = postgres, frontend = react, backend = strapi, link shortener = shlink)

Corresponding to the hering-api https://github.com/scout-ch/hering-api a strapi instance must be developed to allow the operators to manage the content of thilo.

Pre-Requisites

• Additional test data within the solution - #111

How:

• selected scout group (all ages [wölfi - rover]) and users get access to the app
• The feedback is retrieved using the following forms
• Invective: they can shape the future of thilo and win one of five thilo books
• Leaders need to be instructed, so that the tool should be tested in a controlled environment with the scouts. This means that it should be used in a typical Saturday afternoon
• The leaders should ensure that also negative feedback be provided, that there are no consequences of speaking the truth. Ensure unbiased data collection.

Who:

• selected scout group (from wölfe till rovers)
• IT commission
• Thilo Project team

Goal:

• evaluate if the tool us useful
• define features for the next iteration
• define goal of the successor project

Furthermore the following question should be addressed in these tests

• Having low bandwidth / no connection: how does the app behave?

Move current static star maps to d3-celestial to provide more intractability.

Integrate dark mode possibility and theme (white and dark) changer

An additional person supporting this project over a longer period than the project would be extremely enriching. Further concepts such as community driven knowledge and in general future improvement of the app could be beneficially for the whole scout movement:

The person should have minimum knowledge in computer science and web development.

• Is it possible to find a new person, even if the project is ending soon?
• How can the IT com help in this process?
• Project team in lead

Requires defining service workers, depends on #133.

Add further chapters and include more realistic quizzes.

This helps to better see what needs to be further improved and also influence the decisions for the successor project.

How can a print view reader jump to the website at the same chapter?

As simplest approach a QR code could be used pointing to the various chapters within the thilo web app. The links must be as detached as possible, as the solution is tied to the print version. Should be detached from the PBS and from the web app. Therefore a link shortner is placed between the web app and the book. The links are resolved by the link shortner. This allows to further improve the components individually by respecting the interface between them.

Thus thilo should be in the domain name:

• Web App: thilo.scout.ch

• Short Links: thilo.cloud

• Feedback IT kom

• Feedback project team (Broesmel)

• shuffle and present limited set
• hide unnecessary information
• strapi integration
• Add more realistic content for Quiz @aladwani

See chapters: Thilo_Kapitel-Farben see chapters PBS-Thilo_Farben_2022 see colour codes pages

Evaluate a solution to retrieve user feedback from end users in a standardized way.

E.g https://github.com/getfider/fider

• Write Impressum
• Translate into French, Italian

Bessere User Expierence beim Suchen ermöglichen

all UI element wo übersetzt werde münnd, separat vom content:
Z.b. de homepage name (im moment eifach Home), de sidebarnav header, UI labels im allgemeine
die lebed im src/i18n ordner ide *.json files

Requirements

• who access (unique users) from where the app?

Goal

• to measure the usage of the app and the coverage of the app

Evaluate how much work it is to implement a PDF export functionality within Thilo

Currently, we have a static front-end with a pull-only back-end architecture, data being pulled from Strapi.

It would be better if we can integrate Strapi onto a server from where we also host the front-end, to allow for actual browser based caching using Progressive Web Apps, by serving the .json content files from the same location.

Related to #134 and #133.

The current alt-tag image styling needs to be more user friendly and readable.

Current example: [alt: test-image, size: 150pxx150px]

I think mirroring CSS style attributes would be an improvement:

[caption: test-image; width: 150px; height: 150px;]

Furthermore, in the current setup, the style tags are added to a parent div created around the img, which means it will not change the image ratio / the height is ignored when smaller than the width * ratio. This I take is explicitly requested when adding both width and height tags.

The project team terminates the cooperation after completion of the project. How will future improvements regarding code and content be managed?

Or configure react ourselves

CRA support was officially dropped as of 2023.

With the redesign to modernize the UI, I think we can make extensive use of GitHub's Primer Design System.
There is also an interesting note on choosing colors for inclusivity which should factor into our decision on adapting the Thilo colors: https://github.blog/2023-05-11-unlocking-inclusive-design-how-primers-color-system-is-making-github-com-more-inclusive/.

Check if we can include tables like on https://scout-ch.github.io/thilo/#/Pioniertechnik:-Seile --> seilarten

it does not show which answer I have chosen before closing it

@broesmel is there a markup guide where I can change the json file?

Based on the tech stack defined in issue #12 a productive infrastructure must be created. The infrastructure must provide the following services:

• Postgres as a service: for the persistent storage of the backend data and the link shortner

• App Service: for the runtime of both the front- and backend and the link shortner

• CDN: something which is supported by strapi

• What is the current state of the evolution? -> currently the PBS Betriebsplattform project is not ready and therefore productive workload cannot be migrated.

• Where are all the other PBS being moved (away from heroku to ?) -> all of the apps have individual solutions and are not required to be migrated before the PBS Betriebsplattformformen project is concluded

• Challenge productive infrastructure with IT-Kom

• Clarification with PBS to temporally host Thilo within the Azure Infrastructure of the PBS. In clarification at the PBS

• Deploy to PBS Betriebsplattform

Thilo App

• Marketing on Social Media

Thilo Tech Stack

• Contact Pfadi Gloggi: erneut angefragt
• Cudesch Digital: Austausch mit Scattle durchgeführt, Requirements noch nicht klar. Höck am 21.11

How can changes made on one side be migrated / synchronized to the other side?

Refactor the code of the app to make it more clear. Increase reusability and incode documentation (comments)

Within Strapi the Media Library is hosted on Cloudinary. Currently we are using the free-tier which is coming with certain limitations. Within the free-tier 25-credits are available per month.

A credit can be used either for 1,000 Transformations OR 1 GB Storage OR 1 GB Bandwidth.

• What are the current usage of the hering?
• Should we use a PBS wide unique CDN for all applications?
• What are the traffic estiamtes for Thilo? (till the end of the year only a limit number of people will be using the web app for testing and development)

Create a comprehensive markup guide for end users (admins who use the backend to upload and change data)

Extract .png or .svg (from the .ai file) and upload them to Strapi, adding them to the respective sections to the icon entry.

That way I can dynamically load them in the front end and not hard-code them.

thilo_icons.zip

scout-ch/hering#16

Review code for quality and reusability

At exactly 859 px screen width, the header button is shown but the header and it's contents are hidden and the button does not unhide them

candidate: "Roboto"

• header always collapsible
• button instead of header
• sidebar floating
• floating footer with max width, subtle
• floating list buttons, use chapter icons
• content inside the floating is flat
• color and highlight color generation
• colorize bullet points
• colorized table lines
• any highlighted text should be secondary color
• figure out search button / styling - look github for inspo, no border, no shadow, content 'Kapitel durchsuchen'...
• style scrollbars consistenly
• move footer largely inside the sidebar, except for page next buttons

Define what kind of technologies and frameworks are used within the project.

My web browser is set to English. When I load https://scout-ch.github.io/thilo, I get the following page:

I would imagine the same happens for any language other than the available de, fr or it. In the website menu, none of the available languages is selected. Thilo probably needs some proper fallback logic in case the browser language is not available as application language.

(Note: Once I select a locale in the website menu, I automatically get back to this locale on later reloads. But the problem can be reproduced in a new private window.)

Footer placement properly!
next/prev button fixed size

The chapter logo should be visible on the right side of the chapter title.
The logo should be added to the strapi backend (choose a logo per chapter / no must field)