8 ms·
Introducing Podlite, a lightweight block-based markup language
- zagap 3y agoThe specification is licensed under Artistic License 2.0: https://github.com/podlite/podlite-specs https://github.com/podlite/podlite-specs
- Daeraxa 3y agoThis 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?
- zagap 3y agohi! 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+Podlite%0A%0A%3Dbegin+markdown%0A%0A++%23+this+is+markdown+%21%0A%0A%3Dend+markdown%0A https://pod6.in/#p=%3Dtoc+head1%0A%0A%3Dhead1+this+is+Podlit...) thank you!
- Daeraxa 3y agoYeah 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.
- zagap 3y agoAhh, 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 )
- zagap 3y agoThe idea of using short names is interesting: For example: =head1 -> =h1 =item1 * -> =i1 * =item1 [ ] -> =i1 [x] Nice! thank you