Extend callouts to allow longer notes with heading, more than one paragraph, lists etc. #4889

Closed
opened 2026-02-05 09:24:00 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @ilpssun on GitHub (Jul 22, 2024).

Describe the feature you'd like

We use BookStack as a platform for our user documentation. In the docs, we often find that we would like to highlight an important point that should be visualized as a callout. This works fine for single-paragraph notes. However, we often have a situation where we'd like to include either a heading, a second paragraph or even a bullet list of items into the callout. So basically, we'd like to switch from a per-paragraph formatting of callouts to a div-based formatting, which can wrap several h…, p, ul/ol tags.

Currently, a callout with more than one paragraph would look something like this:
image

It is currently visualized as four separate blocks. The requested feature would combine the four “blocks” into a single callout containing a heading, a list and two paragraphs.

Describe the benefits this would bring to existing BookStack users

The benefit from this change is that more complex annotations in user documentation would be supported. I think that this is a typical use-case for more comprehensive documentation projects.

Can the goal of this request already be achieved via other means?

Currently not, as far as I am aware.

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

1 to 5 years

Additional context

No response

Originally created by @ilpssun on GitHub (Jul 22, 2024). ### Describe the feature you'd like We use BookStack as a platform for our user documentation. In the docs, we often find that we would like to highlight an important point that should be visualized as a callout. This works fine for single-paragraph notes. However, we often have a situation where we'd like to include either a heading, a second paragraph or even a bullet list of items into the callout. So basically, we'd like to switch from a per-paragraph formatting of callouts to a `div`-based formatting, which can wrap several `h…`, `p`, `ul`/`ol` tags. Currently, a callout with more than one paragraph would look something like this: ![image](https://github.com/user-attachments/assets/c9309268-6208-44f8-9720-4808163137e7) It is currently visualized as four separate blocks. The requested feature would combine the four “blocks” into a single callout containing a heading, a list and two paragraphs. ### Describe the benefits this would bring to existing BookStack users The benefit from this change is that more complex annotations in user documentation would be supported. I think that this is a typical use-case for more comprehensive documentation projects. ### Can the goal of this request already be achieved via other means? Currently not, as far as I am aware. ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundamental request ### How long have you been using BookStack? 1 to 5 years ### Additional context _No response_
OVERLORD added the 🔨 Feature Request label 2026-02-05 09:24:00 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Jul 22, 2024):

Thank you for the request. Personally I'd prefer to keep the callout formats to be simple block level elements used for calling out rather than have them become more complex containers.

In regards to the state benefit, I'm not too keen on making changes in the name of supporting complexity, since the same justification could be used for any addition to the editor which is not a sustainable approach.

Note, you can create breaks in the via Ctrl/Cmd + Enter to start text on a new line, between this and other inline formatting options, you may be able to emulate what you need.

@ssddanbrown commented on GitHub (Jul 22, 2024): Thank you for the request. Personally I'd prefer to keep the callout formats to be simple block level elements used for calling out rather than have them become more complex containers. In regards to the state benefit, I'm not too keen on making changes in the name of supporting complexity, since the same justification could be used for any addition to the editor which is not a sustainable approach. Note, you can create breaks in the via `Ctrl/Cmd + Enter` to start text on a new line, between this and other inline formatting options, you may be able to emulate what you need.
Author
Owner

@ssddanbrown commented on GitHub (Nov 28, 2024):

I'm going to go ahead and close this off with the reasoning as provided above.

@ssddanbrown commented on GitHub (Nov 28, 2024): I'm going to go ahead and close this off with the reasoning as provided above.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#4889