Write on the left, see it rendered on the right. Windows, macOS, Linux.


TITLE

DESCRIPTION

comment

The editor for Podlite and Markdown. The source stays plain text; the preview
shows what it will look like, side by side, as you type. Open source, and in the store
for every system it runs on:


para

Image

React

=begin React :component<HeaderCol> :id<get>
=for Image :link<https://apps.apple.com/us/app/podlite/id1526511053> :alt('Download on the Mac App Store')
mas_badge_black.png
=for Image :link<https://www.microsoft.com/store/apps/9NVNT9SNQJM8> :alt('Get it from Microsoft')
ms-badge.png
=for Image :link<https://snapcraft.io/podlite> :alt('Get it from the Snap Store')
snap-badge.png
=end React


Or take a build straight from
L<the releases page ↗|https://github.com/podlite/podlite-desktop/releases>.


caption

picture

=begin picture :caption('The source on the left, the live preview on the right') :!link :alt('Podlite Desktop editing a Podlite file')
desktop-podlite.png
=end picture


head

A C<.podlite> file opens as Podlite; a C<.md> file opens as Markdown. The editor
highlights the source in the language it is, and the preview renders it in the same
language. Nothing to switch by hand.


=begin picture :caption('The same window on a Markdown file: Markdown highlighting, Markdown preview') :!link :alt('Podlite Desktop editing a Markdown file')
desktop-markdown.png
=end picture


item

 ============================ | ================ | =================


table

Source code, issues and every build:
L<github.com/podlite/podlite-desktop ↗|https://github.com/podlite/podlite-desktop>.


root

Turn a folder of Podlite files into a static site. The site you are reading is one.


Podlite Web


Convert, render and query Podlite from the terminal.


Podlite CLI


=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 Desktop


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":"0909d0551f9283fadf5251fe798c443dfc2d63c8","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.


Action	macOS	Windows, Linux
New	`Cmd+N`	`Ctrl+N`
Open	`Cmd+O`	`Ctrl+O`
Save	`Cmd+S`	`Ctrl+S`
Save as	`Cmd+Shift+S`	`Ctrl+Shift+S`
Close the window	`Cmd+W`	`Ctrl+W`

Action	macOS	Windows, Linux
Continue a list	`Enter`	`Enter`
Take the item one level in	`Tab`	`Tab`
Take it back out	`Shift+Tab`	`Shift+Tab`
Fold the block	`Cmd+Alt+[`	`Ctrl+Shift+[`
Unfold it	`Cmd+Alt+]`	`Ctrl+Shift+]`
Find	`Cmd+F`	`Ctrl+F`
Undo	`Cmd+Z`	`Ctrl+Z`
Redo	`Cmd+Shift+Z`	`Ctrl+Y`
Follow a link in the source	`Cmd+click`	`Ctrl+click`

Podlite Desktop

Two markups, one editor

What it does

Keyboard shortcuts

Files

Preview

Writing

Where it lives

Action	macOS	Windows, Linux
Show or hide the preview	`Cmd+\`	`Ctrl+\`
Preview beside the source	`Cmd+.`	`Ctrl+.`