microsoft/power-platform-skills / plugins/power-pages/skills/edit-site
edit-site
VerifiedPlans, 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.
references/styling/sources.md
View on GitHub# Styling sources
This index contains original summaries and links, not copied articles or examples. Research context: **September 2026**. Microsoft Learn defines platform support; MVP techniques are supplementary and must be checked against the selected site's actual version and markup. Routine styling uses this bundled guidance. Refresh Learn only for unknown/conflicting/stale guidance or an explicit request; if unavailable, disclose the limitation without inventing newer support.
## Official Microsoft guidance
For exact **component Design-panel** properties, use the bundled [component capability map](studio-component-capabilities.md), including conditional Flex availability. Its scope excludes site-wide themes and other Studio dialogs. The map describes availability, not exclusive ownership: listed and unlisted properties both default to local authoring, with missing/unverified/conditional support warnings retained. Do not promise that custom CSS values populate native controls. Use the official sources below for platform and serialization context.
| Source | Apply it to | Caveat |
|---|---|---|
| [Manage CSS files](https://learn.microsoft.com/en-us/power-pages/configure/manage-css) | Recommends Studio for out-of-box controls; preserves default CSS records and describes custom CSS priority above `theme.css` and below `portalbasictheme.css` | Mention priority for Web File changes, not as a numeric `displayorder` constraint or write prerequisite. Studio guidance is not a VS Code prohibition. Its older 3.3.x-only note conflicts with the dedicated Bootstrap overview |
| [Style your Power Pages site](https://learn.microsoft.com/power-pages/getting-started/style-site) | Theme palette, typography, buttons, and spacing through the Styling workspace | Check the selected site's available controls; do not assume undocumented token names |
| [Customize webpages with the page editor](https://learn.microsoft.com/en-us/power-pages/getting-started/customize-pages) | Paintbrush adjustments generally take precedence over inherited/custom CSS; inspect and edit the actual locally serialized declaration | This motivates local inline edits, not Studio-only routing or blind priority escalation. Authored priority requires explicit justification and review |
| [Advanced CSS](https://learn.microsoft.com/training/modules/power-pages-extend/css) | Exact-page CSS versus reusable CSS Web Files; a `.css` Web File affects its parent and descendants | Historical replacement/customizer examples are not this skill's policy; preserve all default files |
| [Bootstrap overview](https://learn.microsoft.com/power-pages/configure/bootstrap-overview) | Supported versions 3.3.6 and 5 | Inspect referenced local assets; support for v5 does not mean this site uses it |
| [Bootstrap version 5](https://learn.microsoft.com/power-pages/configure/bootstrap-version-5) | Version-specific platform setup and migration context | Setup, migration, framework replacement, and runtime-flag changes are separate tasks |
| [VS Code extension](https://learn.microsoft.com/en-us/power-pages/configure/vs-code-extension) | Supports offline local editing of downloaded site content, Web File creation, and local/remote comparison | Site Preview uses uploaded content and clears cache; do not invoke it as local verification |
| [VS Code for the Web](https://learn.microsoft.com/power-pages/configure/visual-studio-code-editor) | Online content fields and authoring limitations | Remote saves are not local application; the browser editor lacks the Desktop PAC/Node path |
| [Power Platform CLI tutorial](https://learn.microsoft.com/power-pages/configure/power-platform-cli-tutorial) | Standard/enhanced model selection and download/upload separation | Acquisition/deployment are separate workflows; do not execute PAC for normal styling |
| [Create and manage Web Files](https://learn.microsoft.com/power-pages/configure/web-files) | Website/parent relationships, attachments, partial URLs, and visibility | Derive the downloaded schema from verified local records, not a guessed YAML shape |
| [Create a web-template component](https://learn.microsoft.com/power-pages/configure/web-templates-as-components-how-to) | Liquid manifests, includes, and configurable parameters that support maker editing | Preserve existing parameters and editable structure; arbitrary replacement HTML is not equivalent |
| [Custom page layout tutorial](https://learn.microsoft.com/power-pages/getting-started/tutorial-add-custom-page-layout) | Page Copy, template relationships, and localized content | Preserve editable regions and resolve the intended language record |
| [Basic form metadata](https://learn.microsoft.com/power-pages/configure/configure-basic-form-metadata) | Documented CSS Class hooks for control styling | Do not invent a form-wide Custom CSS field or assume all form variants share this metadata |
| [List configuration](https://learn.microsoft.com/power-pages/configure/list-configuration) | CSS Class and Grid CSS Class extension points | Confirm the actual native list and runtime DOM; historical selectors are not cross-version contracts |
## General CSS and bundled parsing
Standard CSS syntax is not a guarantee of Power Pages/browser rendering or native Studio editability. The skill uses pinned bundled **css-tree** rather than fixed property/value/part or gradient-specific grammars. Unknown or semantic-grammar-unverified values produce explicit warnings; fix invalid CSS or verify newer browser support before approval. Never bypass malformed/injected/executable CSS errors or equate missing parser grammar with unsupported Power Pages CSS.
| Public reference | Apply it to | Boundary |
|---|---|---|
| [CSS Syntax](https://www.w3.org/TR/css-syntax-3/) | Structural parsing, escapes, comments, declarations and at-rules | Valid structure is not semantic or runtime proof |
| [CSS Values and Units](https://www.w3.org/TR/css-values-4/) | General units/functions, including calculations | Check target-browser support; not a skill enum |
| [CSS Images](https://www.w3.org/TR/css-images-4/) and [CSS Color](https://www.w3.org/TR/css-color-4/) | Gradient kinds, layers, color spaces and interpolation | Gradient readability needs whole-surface review, not just endpoint contrast |
| [Selectors](https://www.w3.org/TR/selectors-4/) | Stable descendants/states/pseudo-elements | Default component-subtree scoping still applies; global rules need explicit approval |
| [CSS Cascade](https://www.w3.org/TR/css-cascade-5/) | Layers, imports, specificity and priority | Preserve default file order and actual inline winners; validate import placement |
| [MDN CSS reference](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference) | Property/at-rule/browser-support details, responsive rules, fonts and animation | Public compatibility information does not establish this site's live behavior |
| [Reduced-motion preference](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion) | Motion alternatives and accessible animation | Local parsing does not verify effective motion/visibility |
| [css-tree](https://github.com/csstree/csstree) | Maintainer context for the bundled parser and semantic grammar | Use the pinned bundle, not runtime npm installs or automatic downloads |
| [mdn-data](https://github.com/mdn/data) | Pinned shorthand-effects metadata, including logical-side safety | Preserve authored declaration order and review conflicts; metadata is not live rendering proof |
The parser bundle is under `scripts/vendor/css-tools`: `package.json`, `package-lock.json`, `css-tools.cjs` and licenses, including mdn-data's license, travel together. See the plugin [development guide](../../../../PLUGIN_DEVELOPMENT_GUIDE.md#maintaining-the-bundled-css-parser) for the reproducible maintainer build (`npm ci --ignore-scripts`, `npm run build` in that directory). Plugin/site users need no npm installs. Resource URLs still require explicit review; the compiler fetches neither resources nor imports.
## Microsoft MVP perspectives
Attribution context: [Ulrikke Akerbaek's biography](https://ulrikke.akerbak.com/about-me/) and [Engineered Code's About Us](https://www.engineeredcode.com/about-us) identify the authors and MVP background.
| Author and article | Publication context | Useful principle and boundary |
|---|---|---|
| Ulrikke Akerbaek — [How to Style Power Pages](https://ulrikke.akerbak.com/2023/10/04/mppc23-how-to-style-power-pages-my-session-as-a-blog-post/) | 2023; updated September 2024 | Start with the site's native branding and extend deliberately. Do not adopt its numeric display-order workaround or historical font instructions as platform rules. |
| Ulrikke Akerbaek — [Power Pages branding — VS Code, CLI, CSS and SCSS](https://ulrikke.akerbak.com/2022/05/11/power-pages-branding/) | 2022 | Organize shared variables and component styles. SCSS is optional existing-project tooling, not a prerequisite; CLI instructions are historical context. |
| Nicholas Hayduk — [Dynamics 365 Portal Developers — Don't Forget About CSS!](https://www.engineeredcode.com/blog/dynamics-365-portal-developers-dont-forget-about-css) | 2018 | Prefer scoped CSS for presentation-only changes and distinguish hidden content from secured content. Inspect current markup rather than copying legacy selectors. |
| Nicholas Hayduk — [PowerApps Portals: Another UI Change Using Only CSS](https://www.engineeredcode.com/blog/powerapps-portals-another-ui-change-using-only-css) | 2019 | Inspect native list markup before changing presentation and consider mobile behavior. The example uses Bootstrap 3; it is not a reusable Bootstrap 5 patch. |
| Nicholas Hayduk — [Power Pages: Many Layers of Caching](https://www.engineeredcode.com/blog/power-pages-many-layers-of-caching) | 2025 | Distinguish Studio, runtime, browser, and CDN caches when explaining later discrepancies. This does not authorize uploads or cache clearing. |
## Public format evidence
- [Microsoft government app templates, classic portal source](https://github.com/microsoft/gov-apptemplates/tree/64dabc2652a13a2423ee3fb1d6f4bfe8f33fe1d9/portals/core-portal/site): examples of `adx_` metadata and locale-in-filename sidecars.
- [Microsoft Nonprofits, enhanced-model portal source](https://github.com/microsoft/Nonprofits/tree/b3dae27b62620caabf89be3bb91b127177749e80/VolunteerEngagement/Portal-EDM/.powerpages-site): examples of prefixless metadata, nested Web Files, and localization folders.
These pinned snapshots show serialization possibilities, not a one-to-one mapping between data model and filesystem shape. Use original minimal fixtures with placeholder names/identifiers when testing adapters; do not copy real environments, IDs, or entire source pages into examples.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |