/edit-site

name: edit-site
description: >-
  Plans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA
  Power Pages sites created from Microsoft templates or manually in Design Studio. Use for
  requests involving pages, localized content, navigation, assets, snippets, site markers,
  Liquid/web templates, page layouts, or styling. Coordinated work produces an approved
  browser-viewable plan, executes changes in dependency order, verifies the local result,
  and optionally hands off to deployment. Not for React, Angular, Vue, or Astro SPA sites.
user-invocable: true
allowed-tools: Read, Write, Edit, Grep, Glob, Bash, WebSearch, AskUserQuestion, Skill, TaskCreate, TaskUpdate, TaskList, mcp__plugin_power-pages_microsoft-learn__microsoft_docs_search, mcp__plugin_power-pages_microsoft-learn__microsoft_docs_fetch, mcp__plugin_power-pages_playwright__browser_navigate, mcp__plugin_power-pages_playwright__browser_evaluate, mcp__plugin_power-pages_playwright__browser_run_code_unsafe
model: opus

> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding. > For styling-only requests, reuse the result once per installed plugin version in the current conversation.

Customize a Non-SPA Power Pages Site

Coordinate local customization using the component authoring references. Do not duplicate their PAC metadata, identity, serialization, or validation rules.

**Initial request:** $ARGUMENTS

Preview disclosure

Read `${PLUGIN_ROOT}/references/non-spa-preview.md` and apply its **Entry and handoff protocol**. Unless the initial request contains the explicit marker from an actual covered-skill handoff, present the **Customization notice** before site discovery, task creation, or any other project inspection. This notice is informational and does not replace plan or deployment approval. Include `previewNoticeShown: true` and `invocationSource: edit-site` in every covered child-skill request.

Read:

• `${PLUGIN_ROOT}/references/design-studio-site-discovery.md`
• `${PLUGIN_ROOT}/skills/edit-site/references/non-spa-site-authoring.md`

Apply **Request routing** before creating coordination tasks or starting the phases below. For styling-only requests outside a current approved coordinated execution, follow `${PLUGIN_ROOT}/skills/edit-site/references/style-site-workflow.md` and finish after its local verification/report, without the phases below. For an individual page or component request, follow the shared authoring reference and finish after its verification/report. For coordinated work, also read:

• `${PLUGIN_ROOT}/references/site-design-quality.md`
• `${PLUGIN_ROOT}/skills/edit-site/references/customization-plan-contract.md`
• `${PLUGIN_ROOT}/skills/edit-site/references/content-and-page-compositions.md`
• `${PLUGIN_ROOT}/skills/edit-site/references/visual-asset-planning.md`

For coordinated new-site design or requested styling, also read:

• `${PLUGIN_ROOT}/skills/edit-site/references/styling/design-quality.md`

Ownership

For coordinated work, this skill owns:

• selecting one downloaded non-SPA site;
• understanding the complete customization intent;
• resolving cross-operation dependencies;
• generating and obtaining approval for one customization plan;
• executing component workflows in dependency order;
• independently checking the combined local result;
• committing coherent customization units;
• offering deployment after local verification.

It authors webpage, snippet, web-file, web-template, page-template, and site-marker records only through `${PLUGIN_ROOT}/skills/edit-site/references/non-spa-site-authoring.md` and the selected component reference. The `author-webpage-content` skill owns localized body HTML; the `style-site` reference workflow owns guarded styling. It does not upload, activate, or modify Dataverse directly. No dev server, live preview, or generated styling mockup is required. The HTML below is an approval document, not a rendering of the site; local checks cannot prove Studio/runtime appearance.

Progress tracking

For coordinated work, create these tasks before starting:

| Task subject | Active form | Description | |---|---|---| | Discover non-SPA site | Discovering non-SPA site | Select and validate one PAC-downloaded non-SPA site | | Gather customization intent | Gathering customization intent | Resolve pages, content, assets, languages, preservation, and visual direction | | Prepare customization plan | Preparing customization plan | Build persistent JSON and browser-viewable HTML plan artifacts | | Approve customization plan | Reviewing customization plan | Review and approve the complete coordinated local plan | | Execute customization | Customizing non-SPA site | Author components, compose content, and apply styling in dependency order | | Verify customization | Verifying customization | Validate component results, combined references, diff, and Git state | | Complete customization | Completing customization | Commit coherent changes, report local/live state, and offer deployment |

Phase 1: Discover and validate the site

1. Follow the shared non-SPA discovery contract. Accept a site root that is the current directory or a nested directory such as `.powerpages-site/`. 2. Require `.portalconfig/`, non-empty `website.yml`, and at least one non-SPA component directory. Reject `powerpages.config.json`-only SPA sites. 3. If several valid sites remain and request/workspace evidence does not identify one, ask the user to choose. Never select the first filesystem result. 4. Read the site identity, configured languages, existing pages, navigation, snippets, site markers and their page bindings, web files, web templates, page templates, CSS sources, Bootstrap evidence, logos, favicons, existing page imagery, and the exact callers of site-wide brand assets. For header work, resolve the active website header binding, its source/includ