Inconsistent Behaviour of Dialog / Information Boxes in HAJK 4.1

[matself]

Inconsistent Behaviour of Dialog / Information Boxes in HAJK 4.1

In the current release of HAJK 4.1, there are four dialog or information boxes that can be populated with help text, instructions or map-related content. These are configured per map. However, they behave very differently in terms of configuration, editing, HTML/Markdown support and JSON structure. This makes them unnecessarily complex to maintain and prone to errors.

Below is a summary of their current behaviour.

[!] Visa nyheter

Provides an informational dialog with a long description of changes since the previous release.
Not editable in Admin.

(?) Visa hjälp

Provides a help dialog containing a long Markdown example.
This dialog requires JSON-embedded markdown, meaning:

• edited manually inside the map JSON

• characters must be escaped

• newlines must be written as \n

• only a limited subset of markdown is rendered

Not editable in Admin.

(i) Visa informationsruta

Displays a placeholder text.
Supports standard HTML.
Editable in Admin.

:) Introduktionsguide

Opens a guided tour with an animation.
The underlying source mechanism for this is unclear.
Not editable in Admin, but can be enabled/disabled.

---

Summary Table

| Tool name             | Editable in Admin | Can be turned on/off | Understands HTML |
|-----------------------|-------------------|-----------------------|------------------|
| Visa nyheter          | No                | No                    | Yes              |
| Visa hjälp            | No                | No                    | No               |
| Visa informationsruta | Yes               | Yes                   | Yes              |
| Introduktionsguide    | No                | Yes                   | ?                |

---

Problem Summary

The four components use different formats and rules:

• Some use HTML, others Markdown, and one uses a special JSON-markdown format.

• Some are editable in Admin, others require direct JSON editing.

• The behaviour regarding toggling, escaping and rendering is inconsistent.

This increases the overall complexity for administrators and makes documentation harder.

---

Suggested Discussion / Feature Request

It may be valuable to discuss possibilities such as:

• A unified approach for storing and rendering dialog content.

• Clear rules for what should be editable in Admin versus JSON.

• Documentation for the Introduktionsguide format.

• Potential consolidation of overlapping dialog types.

I can provide examples or configuration samples if needed.

[jacobwod]

You're mixing up three different tools.

A) information
The original, admin-editable way of showing some freetext info to the users. Has the limitation of only allowing once instance per map and not allowing MarkDown.

---

B) infodialog
Fixes the two limitations that information has. Due to technical reasons (multiple instances of the same tool in one map), this tool is not edible in the current Admin UI.

---

C) introduction
An entirely different beast: provides an onboarding experience. Has some defaults, but can be overridden in appConfig.json.

---

Also, @matself: please stop posting AI-generated issues/discussion threads. They're easy to generate but use up valuable development time to read and respond to.

[matself]

I note your concern about AI-generated content. I only intended to initiate a well-reasoned discussion based on my actual use of HAJK. If you feel that something was inappropriate or unhelpful, please tell me, so I can format future contributions accordingly.
Also, if there is a better place to for user input, such as requests or suggestions outside of GitHub, I would be happy to contribute there instead.