Skip to main content

Glideshow alpha

Slides you own. A Google Slides–style editor whose decks are plain HTML folders you keep, that AI agents can read and edit alongside you.

A deck is deck.html plus assets/: each slide a <section>, everything on it a positioned box on a 1920 × 1080 canvas. The editor reads and writes that file, an agent can edit it directly (the editor follows live), and the folder presents in any browser. Every save is a version in git.

Install

Needs Python 3.10+ and Chrome; macOS, Linux and Windows.

$ uv tool install glideshow
$ glideshow                        # the home screen: your decks (in ~/decks)
$ glideshow new "Lab meeting"      # a new deck, opened in the editor
$ glideshow build lab-meeting out/ # a copy that presents offline

Or use it online, with nothing to install, at glideshow.org.

Docs

Contributing

Issues and pull requests are welcome. Before sending one, run tools/check.sh (types and lint) and uv run test/smoke.py (the editor end to end, in Chrome).

Releasing

Work lands on main (small changes directly, bigger ones through a short branch and a pull request). Every push to main that passes the checks goes to dev.glideshow.org, the nightly channel. A release is a version tag:

$ # bump `version` in pyproject.toml, commit it, then:
$ git tag v0.2.0 && git push origin main v0.2.0

Run uv run test/smoke.py first. The tag runs the quick checks, deploys glideshow.org and publishes a GitHub Release with notes and the package (0.x versions are marked pre-release). The browser tests also run nightly and on pull requests, as a heads-up. The deploys need the repo secret CLOUDFLARE_API_TOKEN (a Cloudflare token from the "Edit Cloudflare Workers" template) and the variable CLOUDFLARE_ACCOUNT_ID.

License

AGPL-3.0. Use it, change it and share it; if you run a changed version as a service, publish your changes.

Metadata

Release files for glideshow 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for glideshow 0.2.0
File Size Uploaded Provenance Actions
glideshow-0.2.0.tar.gz 914.6 kB Without provenance Details for glideshow-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for glideshow 0.2.0
File Interpreter ABI Platform Actions
glideshow-0.2.0-py3-none-any.whl Python 3 none any Details for glideshow-0.2.0-py3-none-any.whl

Total release size: 1.6 MB

Release files / glideshow-0.2.0.tar.gz

Download URL glideshow-0.2.0.tar.gz
Size 914.6 kB
Tags Source
SHA-256 checksum
How to use checksums
8dd3a35cff9a8cbc1722da1468ffaee90df61f2793c6d4bceb370a8e76c1ae2d
BLAKE2b-256 checksum
How to use checksums
a5a784e10f893191a972d69f6dea9a59b5a37d24e9651b9491ca6f7aba91a69c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / glideshow-0.2.0-py3-none-any.whl

Download URL glideshow-0.2.0-py3-none-any.whl
Size 655.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b57f81f71f65688b31631fabb14931e08a716afc00fa92814132dab899bc26f8
BLAKE2b-256 checksum
How to use checksums
b0a5918c3dd5043ed760084c082efc1304fba2fcf4e895e676675a32830bd2ee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for glideshow 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page