zagap

6 ms·

1.
Show HN: Podlite 2.0 – a block-based markup language with typed blocks(podlite.org)
1 points by zagap 4mo ago|0 comments
2.
Show HN: The Raku Knowledge Base powered by Podlite markup language(Open-Source)(raku-knowledge-base.podlite.org)
8 points by zagap 2y ago|0 comments
3.
by zagap 2y ago
Good question! To meet modern requirements and make documents dynamic, we need a flexible API and integration with contemporary frameworks. Simple HTML just isn't up to the task. Although this was the approach during the early implemen
4.
by zagap 2y ago
This is a wonderful and highly sought-after idea. However, it requires significant resources, so we will definitely come back to it and implement it. Thank you
5.
by zagap 2y ago
The existing typescript implemetation builds a complete AST (Abstract Syntax Tree), over which middlewares are run in several passes. Yes, there are multiple passes over the tree. This is necessary, among other things, to build a table of c
6.
by zagap 2y ago
I agree with you on this. It's a cool feature. What I find most interesting is that there’s no need to choose between Podlite and Markdown; you can use both and switch between them as needed. I think Podlite could be really useful in d
7.
by zagap 2y ago
It's extensible and not tied to any specific programming language, allowing for constructs like this ( mix chunks of markdown and build TOC ): --- =toc head1, head2, head3 =begin markdown # header from markdown ## second level
8.
by zagap 2y ago
This is a specification, it does not declare how implementations work. At the moment only typescript implementation exists and here is PEG grammars from it: https://github.com/podlite/podlite/blob/main/pa
9.
by zagap 2y ago
The specification for the Podlite markup language is written using Podlite markup itself. https://github.com/podlite/podlite-specs/blob/main/Specifica... Also online playground is available here: https
10.
Show HN: Podlite - a lightweight markup language for organizing knowledge(podlite.org)
142 points by zagap 2y ago|47 comments
11.
by zagap 3y ago
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 )
12.
by zagap 3y ago
The idea of using short names is interesting: For example: =head1 -> =h1 =item1 * -> =i1 * =item1 [ ] -> =i1 [x] Nice! thank you
13.
by zagap 3y ago
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+thi
14.
by zagap 3y ago
The specification is licensed under Artistic License 2.0: https://github.com/podlite/podlite-specs
15.
Introducing Podlite, a lightweight block-based markup language(podlite.org)
1 points by zagap 3y ago|6 comments