HackerTrans
TopNewTrendsCommentsPastAskShowJobs

zagap

no profile record

Submissions

Show HN: Podlite 2.0 – a block-based markup language with typed blocks

podlite.org
1 points·by zagap·letzten Monat·0 comments

[untitled]

1 points·by zagap·vor 3 Monaten·0 comments

Show HN: The Raku Knowledge Base powered by Podlite markup language(Open-Source)

raku-knowledge-base.podlite.org
8 points·by zagap·vor 2 Jahren·0 comments

Show HN: Podlite - a lightweight markup language for organizing knowledge

podlite.org
142 points·by zagap·vor 2 Jahren·47 comments

Introducing Podlite, a lightweight block-based markup language

podlite.org
1 points·by zagap·vor 2 Jahren·6 comments

comments

zagap
·letzten Monat·discuss
[flagged]
zagap
·vor 2 Jahren·discuss
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 implementation (https://github.com/zag/js-pod6), it turned out to be a dead end.

thank you
zagap
·vor 2 Jahren·discuss
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
zagap
·vor 2 Jahren·discuss
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 contents (TOC). thank you
zagap
·vor 2 Jahren·discuss
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 document management systems and electronic publishing. But... let's see what practical uses Podlite will find.

thank you
zagap
·vor 2 Jahren·discuss
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
  
 =end markdown
 
 =head1 This is header from Podlite 
---

https://pod6.in/#p=%3Dtoc+head1%2C+head2%2C+head3%0A%0A%3Dbe...
zagap
·vor 2 Jahren·discuss
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/packages/podlit...

At the moment it supports Mermaid diagrams:

https://pod6.in/#p=%3Dbegin+Mermaid++%3Acaption%28%27Caption...
zagap
·vor 2 Jahren·discuss
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://pod6.in/

Thanks for your interest in Podlite! with best, Alex
zagap
·vor 2 Jahren·discuss
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 )
zagap
·vor 2 Jahren·discuss
The idea of using short names is interesting:

For example:

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

Nice! thank you
zagap
·vor 2 Jahren·discuss
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!
zagap
·vor 2 Jahren·discuss
The specification is licensed under Artistic License 2.0:

https://github.com/podlite/podlite-specs