Callout formatting #261

Closed
opened 2026-02-04 18:08:01 +03:00 by OVERLORD · 6 comments
Owner

Originally created by @unknowndomain on GitHub (Feb 7, 2017).

Desired Feature:

Improved formatting for callouts, including:

  • Link colouring to match the style:
screen shot 2017-02-07 at 01 52 18
  • Paragraphs, and other mark down to be suppported.
Originally created by @unknowndomain on GitHub (Feb 7, 2017). Desired Feature: Improved formatting for callouts, including: * Link colouring to match the style: <img width="411" alt="screen shot 2017-02-07 at 01 52 18" src="https://cloud.githubusercontent.com/assets/147143/22674514/3a24fcc4-ecd8-11e6-8e10-dbbc73b1ad90.png"> * Paragraphs, and other mark down to be suppported.
OVERLORD added the 🛠️ Enhancement label 2026-02-04 18:08:01 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Feb 23, 2017):

@unknowndomain Thanks for the suggestion. The link colouring definitely needs to be improved.

What kind of other formatting do your require? Callouts are designed to be simple really and should really only contain a line or two.

@ssddanbrown commented on GitHub (Feb 23, 2017): @unknowndomain Thanks for the suggestion. The link colouring definitely needs to be improved. What kind of other formatting do your require? Callouts are designed to be simple really and should really only contain a line or two.
Author
Owner

@unknowndomain commented on GitHub (Feb 24, 2017):

http://p-i-c.net/books/physical-computing/chapter/physical-computing-for-prototyping

If you look at these week 1/2 pages you can see how we're using them a bit better, this is one of the main formatting problems we have.

@unknowndomain commented on GitHub (Feb 24, 2017): http://p-i-c.net/books/physical-computing/chapter/physical-computing-for-prototyping If you look at these week 1/2 pages you can see how we're using them a bit better, this is one of the main formatting problems we have.
Author
Owner

@aljawaid commented on GitHub (Feb 20, 2018):

@ssddanbrown On pdf export these callout (i) icons are just question marks randomly on the page :(

@aljawaid commented on GitHub (Feb 20, 2018): @ssddanbrown On pdf export these callout (i) icons are just question marks randomly on the page :(
Author
Owner

@ssddanbrown commented on GitHub (Mar 5, 2018):

@aljawaid As of next update they should no longer be question marks but will be blank instead. Will hopefully find a way to include them in the exports.

@ssddanbrown commented on GitHub (Mar 5, 2018): @aljawaid As of next update they should no longer be question marks but will be blank instead. Will hopefully find a way to include them in the exports.
Author
Owner

@ssddanbrown commented on GitHub (Sep 26, 2020):

Thanks to @alexmannuk the link coloring will now be fixed as of v0.30.1, to match the correct callout color.

In regards to deeper formatting, I'd prefer to keep callouts fairly simple and focused in use. Allowing different block styles within makes things more complex to support while opening up callouts for potential misuse in content. Additionally, there has not been much request for more advanced formatting over the last 3.5 years

@ssddanbrown commented on GitHub (Sep 26, 2020): Thanks to @alexmannuk the link coloring will now be fixed as of v0.30.1, to match the correct callout color. In regards to deeper formatting, I'd prefer to keep callouts fairly simple and focused in use. Allowing different block styles within makes things more complex to support while opening up callouts for potential misuse in content. Additionally, there has not been much request for more advanced formatting over the last 3.5 years
Author
Owner

@Felix-Kettnaker commented on GitHub (May 7, 2025):

@ssddanbrown
I would really appreciate this feature.
I was actually using more complex callouts a lot in other note/wiki apps. I see it often times as a kind of tangent marker, something that deviates a bit from the main focus of the page. So it can be a bit longer sometimes.
And from the technical view, blockquotes already allow all the styling. Where is the difference here? Why can't we get that functionality for the callouts also? Why should blockquotes be supposed to be less concise than callouts?

And what qualifies as a "misuse" of callouts - or bookstack in general? I am actually of the opinion that there is no misuse at all in private use and I'm interested in your view on this.

@Felix-Kettnaker commented on GitHub (May 7, 2025): @ssddanbrown I would really appreciate this feature. I was actually using more complex callouts a lot in other note/wiki apps. I see it often times as a kind of tangent marker, something that deviates a bit from the main focus of the page. So it can be a bit longer sometimes. And from the technical view, blockquotes already allow all the styling. Where is the difference here? Why can't we get that functionality for the callouts also? Why should blockquotes be supposed to be less concise than callouts? And what qualifies as a "misuse" of callouts - or bookstack in general? I am actually of the opinion that there is no misuse at all in private use and I'm interested in your view on this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#261