/author-webpage-content

name: author-webpage-content
description: >-
  Generates and fills the localized HTML body of an existing webpage in a PAC
  CLI-downloaded non-SPA Power Pages site from a resolved page-content
  specification. Use whenever a caller has resolved the existing webpage metadata
  and asks to compose, replace, append, or modify
  the exact localized `.webpage.copy.html` file with Design Studio-compatible
  sections, columns, flex containers, text, images, buttons, videos, iframes,
  Generative AI Search components, basic forms, lists, multistep forms, or
  spacers. This skill owns
  only HTML generation and the supplied target file; the coordinator's webpage
  reference workflow owns discovery, records, metadata, languages, routes, templates,
  navigation, and companion-file creation. Do not use for React, Angular, Vue,
  or Astro SPA sites.
user-invocable: false
allowed-tools: Read, Write, Edit, Grep, Glob, Bash, TaskCreate, TaskUpdate, TaskList
model: sonnet

> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding.

Author Webpage Content

Generate and fill one supplied localized Design Studio-compatible webpage body.

**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 project inspection or task creation.

Authoritative references

Always read and follow:

• `${PLUGIN_ROOT}/skills/author-webpage-content/references/webpage-content-composition.md`
• `${PLUGIN_ROOT}/skills/author-webpage-content/references/design-studio-component-authoring.md`

Read only the page-element references used by the requested composition:

• `design-studio-section-layouts.md`
• `design-studio-flex-container-component.md`
• `design-studio-text-component.md`
• `design-studio-image-component.md`
• `design-studio-button-component.md`
• `design-studio-video-component.md`
• `design-studio-iframe-component.md`
• `design-studio-generative-ai-search-component.md`
• `design-studio-basic-form-component.md`
• `design-studio-list-component.md`
• `design-studio-multistep-form-component.md`
• `design-studio-spacer-component.md`

All page-element references are under:

${PLUGIN_ROOT}/skills/author-webpage-content/references/

These references own serialized section and component markup, editing boundaries, preservation, accessibility, and verification rules. Do not invent competing markup contracts.

For an add or edit Generative AI Search component request, target only `{% codecomponent name:Pages.SearchSummary ... %}`. Do not substitute `{% include 'Search' %}`, a Search web template, Search content snippets, the Search Results page record, site markers, or search indexing/settings.

For an add or edit Basic Form, List, or Multistep form request, target only `{% entityform name:'...' %}`, `{% include 'entity_list' key:'...' ... %}`, or `{% webform name:'...' %}` respectively, pointing at a record already present in the downloaded site. This skill does not create the backing basic form, list, multistep form, Dataverse table form/view, or table permissions — see each component reference's **Scope** section. If the named (or implied) record is not found in the downloaded site, do not assist with constructing it: do not query Dataverse (API, SDK, Web API, or CLI) and do not ask the user for IDs, GUIDs, or permissions to assemble it locally. When asking the user how to proceed, the only valid options are (a) embed an existing record, or (b) stop.

Ownership boundary

This skill receives and edits exactly one existing localized file per invocation:

web-pages/<page-directory>/content-pages/<Page>.<locale>.webpage.copy.html

It may compose multiple sections and page elements in that file as one coherent operation.

This skill does not create or modify:

• root or localized webpage YAML;
• page routes, parents, page-template assignments, or navigation;
• page-template or web-template records;
• content-snippet records;
• web files or their metadata;
• basic form, list, multistep form (advanced form/step), Dataverse table

form/view, or table-permission records;

• localized summary, custom CSS, or custom JavaScript companion files;
• another locale unless the request supplies a separately resolved composition

for that locale.

The calling orchestrator must create or confirm the file and resolve its webpage and locale identity before invoking this skill. `edit-site` uses `${PLUGIN_ROOT}/skills/edit-site/references/webpage-authoring.md` for that metadata workflow. This skill does not search for or select a webpage record.

If the target file or any required content, URL, snippet name, or other rendered value is unresolved, stop before writing and return the exact missing input. Do not manufacture a placeholder or expand this skill into metadata or dependency authoring.

Autonomy policy

Complete routine composition without asking the user to approve mechanical details. Infer safe formatting, escaping, indentation, and accessibility details from the resolved specification, authoritative references, existing page markup, and site-local conventions.

Choose independently when safe:

• exact indentation and line endings;
• the documented section serialization matching a named layout;
• component markup matching a resolved element type and source;
• safe link attributes and output encoding;
• preservation of empty columns required by the selected layout;
• the smallest coherent edit for a modification.

Stop before writing when a material choice remains unresolved, including:

• multiple target files, target sections, or components;
• an unresolved section geometry or ambiguous component-to-column mapping, not merely

a layout name missing from the recipe examples;

• missing Flex C