plesty.net is one domain with four surfaces — a public site, per-module docs, a device-booking app, and a module registry. Here's what each is for, how to use it, and how to contribute to it.
🗺 The four surfaces
plesty.net
the public site
Landing pages, the about section, and tutorials — built from the public
website-content repo, so what you read is exactly what contributors merged there.docs.plesty.net/<module>/
per-module reference
Path-based API documentation for every module — each module's Sphinx build lives under its own path, so
docs.plesty.net/plesty-pm100d/ is that driver's reference.manager.plesty.net
device booking
Reserve lab hardware: an availability picker plus atomic multi-device bookings — reserve several instruments as one experiment, with a required log link.
hub.plesty.net
module registry
Browse the curated catalogue of active modules, or query it at
/api/modules/. The registry is swept from GitLab, so listings track the real repos.👤 Using plesty.net
For users
🌐
Read the docs & tutorials
Start at plesty.net for tutorials and the platform overview, then jump to
docs.plesty.net/<module>/ for a specific module's API reference.🔬
Book lab hardware
Sign in to manager.plesty.net, pick an availability slot, and reserve one or more devices as a single atomic experiment — attach the required log link to confirm the booking.
🗃
Discover modules programmatically
Query
hub.plesty.net/api/modules/ for the curated, GitLab-swept registry of active modules — handy for scripting or building on top of the catalogue.🤝 Contributing to plesty.net
For contributors
📝
Change site copy or add a tutorial
Open a merge request against the public
website-content repo — MRs are welcome. You never touch the generator: merging to main rebuilds plesty.net automatically, so the merge is the deploy. Set PLESTY_CONTENT_REPO=local to preview a build against your checkout offline.📚
Publish your module's docs
Write Sphinx docs in your repo; the standard CI
sync docs job builds and publishes them to docs.plesty.net/<module>/ on release — no manual upload.➕
Get your module listed
Publish your module under the
hub group on GitLab; the registry sweep picks it up, and a maintainer flips the curated active flag to surface it on hub.plesty.net.Behind the scenes: the open platform lives on the public GitLab while the operational surface — servers, booking data, registry sync — is self-hosted and private. Same plesty.net domain out front; two very different trust boundaries behind it.