TITLE

para

React

=begin React :component<HeaderCol> :id<header> 
=begin para
=head1 L<Podlite|/>
=for para :id<tagline>
one markup, many possibilities
=para
Podlite is a lightweight block-based markup language designed for flexibility and ease of use.
=end para
=begin para
=for Image
Podlite emblem: a rounded card with two white bars forming an equals sign ./photo.png
=end para

=end React


🎉 New in Podlite 2.0: render CSV as tables, mask content, pre-set block attributes, and more. L<Read more →|file:./blog/202605-podlite-2.0-released.podlite> · L<All news|file:./contents.pod6>


PodLite

=begin PodLite :height<700px> :caption("Try it: type on the left, see it render on the right") :size<large> :enableAutocompletion

=for toc :caption('Table of contents')
  head1, head2, head3 
  
=head2 Space stations
=head3 Life support

Space stations feature I<hydroponic> gardens N<Plants grow without soil,
using mineral nutrient solutions.>, a necessity for B<long-term> missions.

This is an inline formulas example: F< y = \\sqrt{3x-1}+(1+x)^2 >

=for formula :caption('The Cauchy-Schwarz Inequality')
   \\left( \\sum_{k=1}^n a_k b_k \\right)^2 \\leq \\left( \\sum_{k=1}^n a_k^2 \\right) \\left( \\sum_{k=1}^n b_k^2 \\right)

See this L<link|https://en.wikipedia.org/wiki/Cauchy%E2%80%93Schwarz_inequality>

=head2 Diagrams

=begin Mermaid :caption('Diagram with caption')
graph LR
        A-->B
        B-->C
        C-->A
        D-->C
=end Mermaid

=begin comment
This is a commented text.
=end comment

=head2 Lists 

Options B<are>:

=item1  Animal
=item2     Vertebrate
=item2     Invertebrate

=item1  Phase
=item2     Solid
=item2     Liquid
=item2     Gas
=item2     I<Chocolate>

=head2 Tables

=table
    Constants           1
    Variables           10
    Subroutines         33
    Everything else     57

=for table
    mouse    | mice
    horse    | horses
    elephant | elephants

=table
    Animal | Legs |    Eats
    =======================
    Zebra  +   4  + Cookies
    Human  +   2  +   Pizza
    Shark  +   0  +    Fish

=table
    X | O |
   ---+---+---
      | X | O
   ---+---+---
      |   | X

=table
    X   O
   ===========
        X   O
   ===========
            X

=begin table :caption('Super table!')
                        Secret
        Superhero       Identity          Superpower
        =============   ===============   ===================
        The Shoveller   Eddie Stevens     King Arthur's
                                          singing shovel

        Blue Raja       Geoffrey Smith    Master of cutlery

        Mr Furious      Roy Orson         Ticking time bomb
                                          of fury

        The Bowler      Carol Pinnsler    Haunted bowling ball

=end table

=begin markdown

## Header inside markdown
  
$$
\\operatorname{ker} f=\\{g\\in G:f(g)=e_{H}\\}{\\mbox{.}}
$$


 * list 1
   * level 2

=end markdown


  =alias PROGNAME    Earl Irradiatem Evermore
  =alias VENDOR      4D Kingdoms
  =alias TERMS_URLS  =item L<http://www.4dk.com/eie>
  =                  =item L<http://www.4dk.co.uk/eie.io/>
  =                  =item L<http://www.fordecay.ch/canttouchthis>
  
  The use of A<PROGNAME> is U<subject> to the terms and conditions
  laid out by A<VENDOR>, as specified at:
  
       A<TERMS_URLS>

=for code :allow(B)
This I<is> a B<text>


=end PodLite


Podlite also works with AI agents: an agent writes the document, and C<podlite lint> shows where its structure breaks. L<Use with an agent →|/for-agents>


=begin React :component<Showcase> :id<showcase>
=para
=end React


Unbound by any specific domain, programming language, or concept, Podlite stands out as a universal markup language. It's versatile enough to be successfully implemented across various development fields, from web development to scientific research.


head

Use named blocks and typed attributes for content and metadata.


code

=begin code :lang<sh>
npx podlite query 'head1' docs/*.podlite --to json
=end code


C<podlite lint> reports a block left open, with its line. C<podlite test>
checks a document against assertions you write, for example that it has a code
block in a given language.


L<Run lint and query after an agent edits a document: files, commands and output.|https://github.com/podlite/podlite-skills/tree/main/examples/edit-and-check>


Podlite reads C<.md> files as Markdown, and a Podlite document can include a
C<markdown> block.


The L<CommonMark site|https://commonmark.org/> says nothing in Markdown counts
as a syntax error. The L<Podlite specification|/specification> requires a parser
to warn when inline formatting such as C«I<...>» is left unclosed, and
C<podlite lint> reports it with the line.


Web version of Podlite editor - L<pod6.in| https://pod6.in>


picture

=begin React :component<CookieConsent> :id<CookieConsent> :buttonCaption("Got it!")
=para
This website uses cookies for analytics. 
=end React


FOOTER

root

comment

=begin comment
The page template, declared on the root block of index.pod6 and applied to every
page. The navigation component is not imported here: it is declared once in
index.pod6, and the component set is shared across the build, so the block below
finds it by name. A second import would give a second path to the same name and
fail the build.
=end comment


=begin React :component<SpecVersions> :id<versions>
=include doc:SPEC_VERSIONS#versions
=end React


=begin comment
Footer. The mechanism comes from the Raku knowledge base: HeaderCol lays out
every =begin nested :!nested block as a column. The C<< L<empty|#> >> placeholders it
uses to pad columns are not carried over — they print on screen as the word
"empty".

A tool without a page of its own points outward and is marked with an arrow.
=end comment


=begin React :component<HeaderCol> :id<footer>

=begin nested :!nested
=item1 B<Tools>
    =item2 L<Web|/web>
    =item2 L<CLI|/cli>
    =item2 L<Desktop|/desktop>
    =item2 L<Skills ↗|https://github.com/podlite/podlite-skills>
    =item2 L<For agents|/for-agents>

=item1 B<Install>
    =item2 L<Mac App Store ↗|https://apps.apple.com/us/app/podlite/id1526511053>
    =item2 L<Microsoft Store ↗|https://www.microsoft.com/store/apps/9NVNT9SNQJM8>
    =item2 L<Snap ↗|https://snapcraft.io/podlite>
    =item2 L<All releases ↗|https://github.com/podlite/podlite-desktop/releases>
=end nested

=begin nested :!nested
=item1 B<Docs>
    =item2 L<Specification|/specification>
    =item2 L<Quick tour|/quick-tour>
    =item2 L<Roadmap|/roadmap>
    =item2 L<News|/contents>
    =item2 L<RSS|/rss.xml>
=end nested

=begin nested :!nested
=item1 B<Source>
    =item2 L<podlite ↗|https://github.com/podlite/podlite>
    =item2 L<podlite-specs ↗|https://github.com/podlite/podlite-specs>
    =item2 L<podlite-web ↗|https://github.com/podlite/podlite-web>
    =item2 L<podlite-desktop ↗|https://github.com/podlite/podlite-desktop>
    =item2 L<podlite-skills ↗|https://github.com/podlite/podlite-skills>
    =item2 L<pod6.in ↗|https://github.com/zag/pod6.in>
    =item2 L<podlite-vscode ↗|https://github.com/zag/podlite-vscode>
=end nested

=begin nested :!nested
=item1 B<Take part>
    =item2 L<Spec discussions ↗|https://github.com/podlite/podlite-specs/discussions>
    =item2 L<Dev discussions ↗|https://github.com/podlite/podlite/discussions>
    =item2 L<Releases ↗|https://github.com/podlite/podlite/releases>
    =item2 L<Playground ↗|https://pod6.in>
=end nested

=end React


=begin comment
The legal line comes last and is separated by a rule — the order is taken from
Apple's documentation: map first, legal second. In the site source it lives in
=FOOTER and therefore printed above the map; the build moves it here.
=end comment


Podlite   


data

=begin data :id<versions>
[{"ref":"v1.0.1","prefix":"v1.0","label":"v1.0","state":"past","index":true,"sha":"e3c97ffad2f6d20f0fc916477a6c6f6f876f14d3","sourceUrl":"https://github.com/podlite/podlite-specs/tree/v1.0.1","order":0},{"ref":"main","prefix":"v2.0","label":"v2.0","state":"current","index":true,"sha":"6f447d8b4f9c05986d55d0e75e6de81fa8aa5f21","sourceUrl":"https://github.com/podlite/podlite-specs/tree/main","order":1},{"ref":"release/v3.0","prefix":"v3.0","label":"v3.0","state":"upcoming","index":false,"sha":"dab44a8a7df1f8756614e461d0dee202e889ae65","sourceUrl":"https://github.com/podlite/podlite-specs/tree/release/v3.0","order":2}]
=end data


nested

L<Funding ↗|https://opencollective.com/podlite> pays for the time that goes into Podlite.


Podlite

Podlite Desktop

Podlite Web

Podlite for agents

Podlite CLI

Write structured documents

Select blocks by name and attributes

Run checks after an edit

Bring your Markdown

Why blocks

Web version of Podlite editor - pod6.in