Websites built by asking.
Pages is the part of Plexara that serves websites and web apps. Describe what you want to the PBS SoCal MCP (Plexara) and it builds it, publishes it to a private working copy, and moves it to the version people use when you say it's ready, on a pages address, an internal subdomain or a domain of your own.
What Pages is for
Anything your team would otherwise send as a stack of attachments, a slide deck nobody can find, or a request for web help.
Team hubs and intranets
A home for a department: who to ask, how things are done, links to the reports people use every week.
Campaign and project sites
One place for a pledge drive, an event or a launch, with pages for each piece and a review stage before anyone else sees it.
Guides and documentation
Step-by-step how-tos like this one, kept as one site instead of scattered documents.
Media and asset libraries
Galleries of show art, event photos and downloads, served from the shared brand and media library.
Part of Plexara
Plexara is an agent-first platform that sits on top of PBS SoCal's Data Estate: the warehouse, the source systems, the automations that keep them current, and the knowledge about what the data means.
You work with Plexara by asking. The PBS SoCal MCP (Plexara) is how Claude reaches it, with your own access and nothing more. Reports, dashboards, automations and now websites are all things you ask Plexara for, and they all live in the same governed place.
Pages is where those websites run. A page can be a plain document, or the front of a Plexara Application with its own database, live data and forms.
- Agent-firstEvery site is built, changed, reviewed and shipped by asking. No web server, no deploy pipeline, no developer queue.
- On the Data EstatePages can show live PBS SoCal data, read as the person viewing, through the same permissions as everything else in Plexara.
- Any domainA private pages address, an internal subdomain like
team-news.pmgsc-data.org, or a custom domain such asexample.com. - GovernedPrivate by default, every release kept, every change reviewable, and nothing public without the owner or an administrator.
Not just static websites
Pages serves anything a browser runs, and a site can be part of a Plexara Application with endpoints, a database and forms. These three run on live PBS SoCal data.
TV schedule
Three channels, three weeks, show posters and what's on now. Each day loads in milliseconds.
Reach dashboard
Nielsen reach by channel and month, and last month's top shows, refreshed on a schedule.
Suggest a show
A form that stores to the application's database: you see your own suggestions, everyone sees the tally.
Three ideas cover almost everything
Read these three and the rest of this guide is detail.
1. Changes land in dev
Every edit goes to a working copy called dev. Nothing people rely on changes until you promote it.
2. Promote what's ready
When dev looks right, promote moves that exact version forward, one step at a time, to prod. Roll back in one step if you need to.
3. Private until you say otherwise
Every site asks for the PBS SoCal sign-in and opens only for the people you share it with.
The flow, start to finish
The same path every site takes, whether it's one page or a thousand.
Ask
Tell the PBS SoCal MCP (Plexara) what you want. It writes the pages.
dev
site--dev.pages…Review the working copy. Ask for changes until it's right.
prod
site.pages…Promote it. Share it with your team, or serve it on any domain.
Where to go next
Pick the path that fits what you need today.
Tutorial
Build, review, share and promote your first site in about ten minutes.
How it works
Addresses, releases and what happens when someone opens your site.
Environments
Dev, stage and prod, promoting, rolling back and approvals.
Security
Sign-in, sharing, roles, public domains and the protections built in.