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.2

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.2
File Size Uploaded Provenance Actions
glideshow-0.2.2.tar.gz 916.5 kB Without provenance Details for glideshow-0.2.2.tar.gz

Built distribution (wheel)

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

Total release size: 1.6 MB

Release files / glideshow-0.2.2.tar.gz

Download URL glideshow-0.2.2.tar.gz
Size 916.5 kB
Tags Source
SHA-256 checksum
How to use checksums
0d0e6a721bddbe0d48dd53c87c422a0d87cc4394b137193fe0abdb54e2d06d8c
BLAKE2b-256 checksum
How to use checksums
0448ad95a8b451dc902ba77d3df0c52497ca270719982de73892b0a45910ca35
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.2-py3-none-any.whl

Download URL glideshow-0.2.2-py3-none-any.whl
Size 655.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ba656a8a1c05ee74aacdfcba8f8f6d754150623dc4a13703478f8cb330c9b547
BLAKE2b-256 checksum
How to use checksums
fd528d90467debb8536d1d715f65fa2f1c651bfe3b38398be8ac6a2cc5ef182a
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.2

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