A screenplay community should expose real work, with explicit permission
Screenwriting advice becomes concrete when readers can study pages: how a scene heading establishes production information, how action paragraphs control pace, where a reversal lands, and what changed between an idea and a draft.
Laper's open screenplay community is a product surface for published projects. It is not a set of invented demo cards. The community panel requests actual public works from the backend, paginates them, and opens a project detail modal. Public script access can load the serialized screenplay snapshot needed to read the work.
The essential boundary is publication. A project must be intentionally public before the community services expose it.
Visibility is checked on the server
The backend distinguishes public work from private, invite-only, and link-shared access. Community listing is for public published projects. Public script services apply their own visibility rules when serving a direct reading link.
This means a visual “public” badge in the browser is not the security control. Server services and repositories decide whether the project can be listed or read.
The project owner also controls collaboration and export-related permissions separately. Public reading does not automatically grant edit access to the original project.
What a community member can do
The current community system supports a focused interaction model:
| Action | Availability |
|---|---|
| Browse public projects | Public listing endpoint with pagination |
| Read a public project | Public project detail and screenplay snapshot when visibility permits |
| View comments | Public comment-list workflow |
| Add or delete a comment | Authenticated community workflow |
| Like or unlike a work | Authenticated, server-owned counter workflow |
| Copy a project | Authenticated workflow, subject to public permissions |
Copying creates a new project for the member. It does not grant a stranger a CRDT editing session inside the author's original. That separation makes remix and study possible without confusing them with collaboration.
For invited co-writing inside one authoritative project, read real-time screenplay collaboration.
Reading is more useful when structure remains intact
A public screenplay is not just a PDF image. Because Laper's script is built from typed nodes, the reading surface can preserve screenplay structure and project identity. Views, comments, likes, and copies refer to a real project rather than a marketing sample disconnected from the application.
That also creates a path from education to practice:
- study a public script's page and structure;
- discuss a scene or revision choice;
- copy an allowed work into a separate private project when remix is appropriate;
- revise without changing the published original;
- publish a new project only when its owner chooses to.
The community does not claim that every public script is professionally vetted or that popularity equals quality. Ranking and engagement are discovery signals, not artistic verdicts.
Comments and likes are durable application data
Community interactions live in backend tables and RPCs, not in Supabase Realtime channels and not inside the screenplay CRDT. That is the correct separation: comments on a public project, like counters, and copy counts are application records; screenplay content is document state.
Keeping those responsibilities distinct avoids a common architecture mistake where every live-looking feature is forced into one synchronization system. Loro owns collaborative project documents. The community API owns public discovery and interaction.
Publication should remain deliberate
Writers need confidence that a draft does not become public because they opened a community tab or invited a collaborator. Public access is a project choice. Invite collaboration, link sharing, and public publishing have different meanings and should keep different gates.
Laper's community is therefore “open” at the library boundary, not at the privacy boundary. It makes intentionally published screenplays readable and discussable while leaving private work private.
Return to the AI screenwriting software overview, browse the core advantages, or study established craft in the Laper Blog.