Comment by Daeraxa | Hacker News Reader

Comment by Daeraxa | Hacker News Reader

Parent Full thread

This is pretty neat, my only real gripe (and I know it is inherited from pod) is that the formatting tags can make it a bit difficult to read compared to plain Markdown, especially in the middle of text.

For example the line in the online editor:

This I<is> a B<text>

I find a little difficult to read at a glance.

The list items are also a bit visually "noisy" with every item needing its own "=itemX".

Is the plan to stick to the existing pod style rigidly or is there any potential flexibility for the syntax in the future?

hi! Markdown is part of Podlite, so you can always switch to markdown mode:

=begin markdown

# I love markdown \o/

   * item 
   * item

 =end  markdown

[example](https://pod6.in/#p=%3Dtoc+head1%0A%0A%3Dhead1+this+is+Podlit...)

thank you!

Yeah I get that markdown is included in its own block, was just thinking about the non-markdown syntax and really what the plan is in general - i.e. are you looking to keep pod6 compatibility or are you looking to use the overall style but maybe deviate from the some of the basic standards.

Ahh, yes, of course, there are no dogmas here, I think all options are possible. After all, this is just the beginning of the journey I think for Podlite )

The idea of using short names is interesting:

For example:

=head1 -> =h1 =item1 * -> =i1 * =item1 [ ] -> =i1 [x]

Nice! thank you

Reply on news.ycombinator.com