Documentation Integration #2980

Closed
opened 2026-02-28 03:13:46 -05:00 by deekerman · 1 comment
Owner

Originally created by @extrafein on GitHub (Jan 1, 2024).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

As a Administrator I want the possibility to get - in case of an incident - as fast es possible to the corresponding documentation, to reduce downtime as much as possible

✔️ Solution

In my use case a notes-section inside each monitor would be more than helpfull. This section should interpret markdown-code to enable deeper integration via hyperlinks.

Alternatives

Add some text into the description of the monitor.
But:

  • The idea of this fiel is to descripe the service and its intention in 1-2 sentences
  • No Markdown / hyperlinks possible

📝 Additional Context

EXAMPLE

Typical issues and solutions

Main Dokumentation

Originally created by @extrafein on GitHub (Jan 1, 2024). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description As a Administrator I want the possibility to get - in case of an incident - as fast es possible to the corresponding documentation, to reduce downtime as much as possible ### ✔️ Solution In my use case a notes-section inside each monitor would be more than helpfull. This section should interpret markdown-code to enable deeper integration via hyperlinks. ### ❓ Alternatives Add some text into the description of the monitor. But: - The idea of this fiel is to descripe the service and its intention in 1-2 sentences - No Markdown / hyperlinks possible ### 📝 Additional Context # EXAMPLE ## Typical issues and solutions - **This is the issue**: [Typical soultion](#) ## Main Dokumentation - [Configuration](#)
Author
Owner

@CommanderStorm commented on GitHub (Jan 1, 2024):

I think this should be is a part of #646 => closing as a duplicate

Related #3008

@CommanderStorm commented on GitHub (Jan 1, 2024): I think this should be is a part of #646 => closing as a duplicate Related #3008
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2980
No description provided.