Organizing scripts
Early days. This is the part of the product still being figured out. Scripts, teams and permissions work as described; the way they are grouped is going to change, and this page will change with it. Nothing here is a promise about how it will look in six months.
A script owns its own path
Every script lives inside a team, and the URL says so. The prompter is one tool for working on that script rather than the thing the script belongs to.
That last segment is deliberately the shallow one. The other tools a script will grow — an editor, the deck, research notes — hang off the same root rather than each inventing a section of the site for themselves.
Projects — planned
A team accumulates two shapes of work, and today they sit in one flat list. This Week in PHP Internals is a series: an episode a week, sharing a format and differing mostly by date. Your Enums Are Boring is a one-off, rewritten for each conference it is given at.
The intent is a project layer between the team and its scripts, so a team's home page becomes a list of projects rather than a list of every script ever written.
Scripts currently sit directly under the team, which works fine until a team has more than a screenful.
Who can do what
Anyone in a team can open that team's scripts in the prompter, whatever their role. Reading is not a permission here: a team filming together all needs to be able to run the show. What roles control is who can change things.
| Can | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| Open and run every script | ● | ● | ● | ● |
| Change a script | ● | ● | ● | · |
| Invite people, and cancel invitations | ● | ● | · | · |
| Rename the team | ● | ● | · | · |
| Add, change or remove a member | ● | · | · | · |
| Delete the team | ● | · | · | · |
Changing a script is the only line an editor holds and a viewer does not. Nothing enforces it yet, because nothing in the app can edit a script yet — the roles express the distinction ahead of the feature that needs it.
People join by invitation, sent to a specific address and only usable by that address. Registration is invitation only while the product is in early access, so an invitation is currently the only way in.
What is not settled
Where scripts live
Today they are files. A database or object storage would both work, and the prompter would not notice which.
Where editing happens
Here, or in your own editor with the app watching for changes. The prompter already reloads a script that moved underneath it.
How episodes relate
Shared boilerplate, a template, or nothing at all. A weekly show wants one of those; nobody has proven which.
If you have opinions about any of that, early access is the right moment to have them.
Want to run your next take on this?
PteroPrompter is in early access. Leave an address and we'll be in touch when the first takes ship.