microsoft/power-platform-skills / plugins/power-pages/skills/author-webpage-content
author-webpage-content
VerifiedGenerates 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.9 KB |
| references/design-studio-basic-form-component.md | markdown | 4.5 KB |
| references/design-studio-button-component.md | markdown | 10.2 KB |
| references/design-studio-component-authoring.md | markdown | 4.3 KB |
| references/design-studio-flex-container-component.md | markdown | 4.2 KB |
| references/design-studio-generative-ai-search-component.md | markdown | 5.4 KB |
| references/design-studio-iframe-component.md | markdown | 8.0 KB |
| references/design-studio-image-component.md | markdown | 10.7 KB |
| references/design-studio-list-component.md | markdown | 5.6 KB |
| references/design-studio-multistep-form-component.md | markdown | 5.1 KB |
| references/design-studio-section-layouts.md | markdown | 11.9 KB |
| references/design-studio-spacer-component.md | markdown | 7.9 KB |
| references/design-studio-text-component.md | markdown | 8.8 KB |
| references/design-studio-video-component.md | markdown | 11.1 KB |
| references/webpage-content-composition.md | markdown | 13.6 KB |
references/design-studio-basic-form-component.md
View on GitHub# Basic Form Component
Use this reference only to add or edit the markup for the **Form** component (the
underlying Dataverse/PAC record and serialized folder are named **Basic Form**):
```liquid
{% entityform name: '<basic form name>' %}
```
This component renders one existing basic form record. This reference does not cover the
Multistep form component (`{% webform name: '...' %}`, see
`design-studio-multistep-form-component.md`) or the List component
(`{% include 'entity_list' ... %}`, see `design-studio-list-component.md`).
## Scope: reference an existing basic form only
The **+ New form** flow creates a new Dataverse table form, a table-permission
record, and the basic form record itself — none of which can be authored from local YAML
alone. This skill therefore only inserts, moves, or edits the `{% entityform %}` tag that
points at a basic form **already present in the downloaded site**:
```text
basic-forms/<basic-form-directory>/<basic-form-directory>.basicform.yml
```
If the request needs a basic form that is not already downloaded, do not create a
`.basicform.yml`/`.basicformmetadata.yml` pair locally to simulate it, and do not query
Dataverse (API, SDK, Web API, or CLI) or ask the user for a Dataverse form ID, table
permission, or any other record detail in order to assemble it yourself — this skill only
references a form already serialized under `basic-forms/` by a prior `pac pages download`;
it does not help construct, fetch, or synthesize one. Stop and tell the user to create the
form in the Data workspace, Design Studio, or the Management app and re-download the site
before this component can reference it. Do not invent a plausible-looking form name. If
asking the user how to proceed, never present "create a new form" as a selectable option —
only embedding an existing form, or stopping, are valid choices.
## Resolving the exact form name
1. List `basic-forms/` and find the directory matching the request.
2. Read `<directory>.basicform.yml` and use its exact `adx_name` value as the tag's `name`
argument — not the directory name, which PAC CLI can slugify or truncate.
3. Note `adx_entityname` (the bound Dataverse table) to confirm it matches the request's
intended data source.
4. An empty `{% entityform name: '' %}` tag is a valid state (a Form component added
without selecting a backing form yet); treat it as unresolved, not as evidence of a
broken page.
## Markup
```liquid
{% entityform name: 'Simple Contact Us Form' %}
```
- Place the tag directly inside the selected `.columnBlockLayout` or Flex Container.
- Treat it as a leaf component; do not add child markup, duplicate field markup, or a
hand-written `<form>` around it.
- Allow multiple instances of the same basic form on one page only when the request asks for
it; by default, treat each basic form as rendered once per page.
- Do not impose a column width, breakpoint, padding, or margin.
- Escape the selected Liquid string delimiter.
- Preserve existing attribute order and quote style when editing.
## Requirements
- The basic form's bound table must already have table permissions configured for the
intended web roles; this component does not create them.
- Attachment, CAPTCHA, AI form-fill, and code-component field settings live on the basic
form/Dataverse-form record, not in the `.webpage.copy.html` markup. Do not attempt to
express them as additional Liquid attributes.
- `adx_entityformid` binds the basic form to its Dataverse form definition; do not edit it
through this component — that is a basic-form-record change, not a page-content change.
## Editing
Identify one exact `{% entityform name:'...' %}` tag by page, section, column, and nearby
content. Change only the requested tag (its `name`, or its position). Preserve surrounding
Liquid, HTML, siblings, indentation, and line endings. Do not retarget a tag to a different
basic form unless the request explicitly asks for that record swap.
## Verification
1. Confirm the tag uses `entityform` (not `webform` or `include 'entity_list'`).
2. Confirm `name` exactly matches the target basic form's `adx_name`.
3. Confirm each requested instance appears once in the correct position.
4. Confirm unrelated content, other locales, and other pages are unchanged.
## Documentation
- [Add forms](https://learn.microsoft.com/power-pages/getting-started/add-form)
- [Tutorial: Add a form to a page](https://learn.microsoft.com/power-pages/getting-started/tutorial-add-form-to-page)
- [Configuring table permissions](https://learn.microsoft.com/power-pages/security/table-permissions)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |