PBS SoCal Plexara Pages
Start a site

Understand Pages

Environments

What is Plexara?

Plexara is the agent-first platform on top of PBS SoCal's Data Estate. Pages is the part of Plexara that serves websites and web apps.

Read the overview

Get started

What it can do

Try it now

Ask the PBS SoCal MCP (Plexara): "Create a site called team-news, publish a one-page welcome, and give me its dev address."

More prompts

Live examples

How they work

Real data, real speed

Every example reads live PBS SoCal data through a Plexara Application, as you, in milliseconds.

Open the schedule

Who sees what

Under the hood

The short version

Every site starts private. Only people you share it with can open it, and only the owner or an administrator can make one public.

Read the security overview
Pages / Build

Tutorial: your first site

About ten minutes, start to finish. You'll create a site, review it, change it, share it and promote it, all by asking the PBS SoCal MCP (Plexara) in Claude.

Before you start

  • You need Claude with the PBS SoCal MCP (Plexara) connected, the same connection you use for reports and data questions.
  • Your account needs permission to build sites. If the MCP tells you that you can't manage sites, ask the PBS SoCal data platform administrators to turn it on for you.
  • Pick a name. Site names are lowercase letters, numbers and single dashes, like pledge-drive or team-news: at least three characters, at most 57, and never two dashes in a row.

  1. Create the site and publish a first version

    Describe what you want in plain words. Say who it's for and what should be on it. The MCP creates the site (you become its owner), writes the pages and publishes them to dev.

    Ask the PBS SoCal MCP (Plexara)Create a new site called team-news. Publish a one-page welcome for the Marketing team with the PBS SoCal logo, a short intro, and three sections: this week's priorities, who to ask, and useful links. Tell me its dev address.

    The answer includes the site's addresses. The one ending in --dev.pages.plexara.pmgsc-data.org is your working copy.

    Using the PBS SoCal brand. Ask the MCP to "mount the global brand folder at /brand/" and the official logos and PBS Sans fonts are available to every page, without copying files into the site.

  2. Switch on the addresses

    On PBS SoCal, a new site's addresses are switched on at the network edge by an administrator, who also issues their security certificate. Send the data platform administrators your site's name; it takes about a minute once they have it. You only need to do this when you create a site, add an environment or add a domain, not for each change.

  3. Review it in dev, and ask for changes

    Open the dev address. You'll be asked to sign in if you aren't already. Look at it on your phone too.

    Then ask for changes the way you'd ask a colleague. Each change makes a new release in dev; nothing anyone else uses is affected.

    Ask the PBS SoCal MCP (Plexara)On my team-news site, add a "Wins this month" section under the intro, and make the useful links a two-column list.
    Ask the PBS SoCal MCP (Plexara)What changed between release 1 and release 2 of team-news?

    For small fixes, the MCP edits just the affected page in place instead of re-sending the whole site.

  4. Share it for review

    Share dev (or a stage environment, if you add one) with the people who should look at it before it goes wider. View access lets them open it and nothing more.

    Ask the PBS SoCal MCP (Plexara)Share the dev environment of team-news with my manager, by their PBS SoCal email, view only.

    To let a teammate work on the site with you, give them manage access instead. Managers can publish, promote and share, but can't make anything public or delete the site.

  5. Promote it to prod

    When dev looks right, promote it. prod now serves exactly the release you reviewed, at the site's main address, team-news.pages.plexara.pmgsc-data.org.

    Ask the PBS SoCal MCP (Plexara)Promote team-news from dev to prod, then share prod with everyone internal.

    Keep working in dev. Prod only changes when you promote again, and you can roll it back in one step.

  6. Optional: give it a domain

    For a shorter address, add a domain to prod: an internal subdomain such as team-news.pmgsc-data.org, or a custom domain such as example.com once its DNS points at Plexara. It's added private, so it still asks for a sign-in. An administrator switches it on, the same as in step 2.

    Ask the PBS SoCal MCP (Plexara)Add the domain team-news.pmgsc-data.org to the prod environment of team-news, private.

    Only the owner or an administrator can make a domain public. Read Making a site public first.

Prompts to copy

Swap in your own site name. The MCP knows the rules on this site, so you don't need to name commands.

Building

CreateCreate a site called pledge-drive with pages for Home, Schedule, Thank-you gifts and FAQ, using the PBS SoCal brand. Publish it to dev.
Generate pages from a listOn my show-guide site, make one page per show from this list, with a shared layout, and an index page that links to all of them.
Copy an existing siteCopy https://www.example.com into dev on a new site called example-archive.
Add imagesMount my folder "pledge-drive/photos" at /photos/ on the pledge-drive site and add a gallery page that uses them.

Reviewing and releasing

StatusShow me the environments of pledge-drive, the release each one serves and who can open each.
Add a review stepAdd a stage environment to pledge-drive between dev and prod, and require approval for prod.
PromotePromote pledge-drive from dev to stage.
UndoRoll back prod on pledge-drive to the release it served before.

Access

Who can see itWho can open each environment of pledge-drive?
Remove accessRemove my former intern's access to pledge-drive.