4 ms·

True. Wide-adoption makes markdown hard to beat. However, I _would_ like to see a better alternative. My #1 feature request would be simple styling (beyond bol

True. Wide-adoption makes markdown hard to beat. However, I _would_ like to see a better alternative. My #1 feature request would be simple styling (beyond bold, italic, etc.) Specifically, some way to compactly color and highlight text. Something like [C#4c4|aaa]Text[/C] maybe where format is #{text-color-rgb}|{background-color-rgb} where background is optional. Likewise, something similar for font like [F:10pt,monospace]Test[/F]. Extra credit for named styles: [$danger=C#484|#cc8] and then [S:$danger]I'm dangerous[/S].

al_borland 1y ago
The problems with this ends up being the result becomes less human readable. At some point, why not just write HTML? You already have open and close brackets in your example. This is HTML with extra steps. If the issue is the extra effort in typing some extra characters, emmet solved this a decade ago.
Forgret 1y ago
Thanks for the idea, it sounds interesting, I'll try to simplify the syntax for better understanding. 1. Inline styling with @ @color#4c4,bg#aaa Text @ color#hex for text color bg#hex for background color Multiple props separated by commas Ends with another @ (so you can nest easier without clashing with brackets) Example: @color#fff,bg#f00 Danger!@ 2. Fonts with @font @font10pt,mono Code sample@ 10pt = font size mono = monospace (could also be serif, sans) 3. Named styles @style$danger=color#484,bg#cc8@ @danger I'm dangerous@ First line defines the style name Second line uses it with just @name …@ jones1618 What do you think?
- jones1618 1y ago
  Sounds good! My only observation is that, wherever possible, make it easier to see/scan-for text content. So my text gets lost a bit in: @a-bunch-of-markup My Text is here@ Maybe add a visual delimiter, so: @a-bunch-of-markup:My Text is here:@ To my eye, this makes my content text stand out more clearly.

al_borland 1y ago

The problems with this ends up being the result becomes less human readable. At some point, why not just write HTML? You already have open and close brackets in your example. This is HTML with extra steps. If the issue is the extra effort in typing some extra characters, emmet solved this a decade ago.

Forgret 1y ago

Thanks for the idea, it sounds interesting, I'll try to simplify the syntax for better understanding. 1. Inline styling with @ @color#4c4,bg#aaa Text @ color#hex for text color bg#hex for background color Multiple props separated by commas Ends with another @ (so you can nest easier without clashing with brackets) Example: @color#fff,bg#f00 Danger!@ 2. Fonts with @font @font10pt,mono Code sample@ 10pt = font size mono = monospace (could also be serif, sans) 3. Named styles @style$danger=color#484,bg#cc8@ @danger I'm dangerous@ First line defines the style name Second line uses it with just @name …@ jones1618 What do you think?

jones1618 1y ago
Sounds good! My only observation is that, wherever possible, make it easier to see/scan-for text content. So my text gets lost a bit in: @a-bunch-of-markup My Text is here@ Maybe add a visual delimiter, so: @a-bunch-of-markup:My Text is here:@ To my eye, this makes my content text stand out more clearly.