Create and edit non-SPA Power Pages sites with Agentic Coding tools

We’re pleased to introduce preview support for Power Pages sites built with web templates and Liquid (non-SPA or traditional portals). With the Power Pages plugin for GitHub Copilot CLI and Claude Code, describe the site you want to create or edit. The plugin helps you build pages, update content and templates, and customize styling.

The plugin previously focused on creating single-page applications (SPAs) with React, Angular, Vue, and Astro. This update brings the same conversational approach to sites using web templates and Liquid, without requiring an SPA rewrite.

You can develop sites alongside makers in Power Pages design studio and continue to work with the site structure and components you already use.

Note

Non-SPA site creation and customization using the plugin are in preview. Supported templates, components, and workflows may change. Try the experience in a non-production environment, keep downloaded files under source control, and review changes before deployment.

This preview applies only to these plugin workflows, not to Power Pages, the design studio or the plugin for authoring SPAs.

What’s new

• Create from a Microsoft-provided site template. Choose a supported template labeled Non-SPA to create a site using web templates and Liquid. The plugin guides you through creating and downloading the site.
• Edit without an architecture rewrite. Use /edit-site with a site downloaded through Microsoft Power Platform CLI (PAC CLI), including sites created in design studio.
• Update pages and shared content. Add pages and navigation, update content in your site’s languages, edit reusable content snippets and web templates, and customize styling.
• Review before you publish. For changes across multiple pages or components, review a customization plan in your browser. Local edits don’t update the live site. Deployment requires separate approval.

How it works

Create a site, then make it your own

Start with a request such as:

Create a Power Pages site using web templates and Liquid (non-SPA) for community program registration.
Use a supported Power Pages template, then help me customize the home page with our branding and a clear path to registration.

Choose a supported template and confirm your environment, site name, language, subdomain, and download folder. Review and approve the plan before the plugin creates a website in your environment.

The plugin then downloads the site with PAC CLI, verifies the website identity and Bootstrap files, and saves the original files in Git. Continue with local customization or keep the template unchanged.

The template is a starting point and not a fixed design. Customize page layouts and branding while reusing the native forms, lists, content snippets, and data connections your site needs.

New non-SPA creation uses the enhanced data model with Bootstrap v5.0. An environment administrator must verify that Switch to enhanced data model is enabled. The plugin doesn’t change this shared environment setting for you.

Update the site you already have

Open your downloaded site in GitHub Copilot CLI or Claude Code and describe a change:

Add an FAQ page to this downloaded Power Pages site that uses web templates and Liquid and include it in the navigation. Use the site's existing language and visual style. Ask me to confirm any policy details you need.

For a broader update, you can ask:

Refresh the home and about pages with our supplied branding. Update the shared header and footer and preserve the existing sign-in behavior and data-bound components.

The plugin checks the relevant pages, templates, files, and references. For changes across multiple pages or components, review one plan covering what will change and what will stay unchanged. Smaller requests use a focused workflow.

Note: You can edit downloaded sites that use either the standard or enhanced data model. The editing workflow doesn’t change your data model, replace Bootstrap, or convert your site to an SPA.

Deploy when you’re ready

Review your local file changes and any reported limitations. When you’re ready to update the website, run /deploy-site and approve the upload.

For sites using web templates and Liquid, the plugin uses pac pages upload. It confirms the target environment and website identity and specifies the data model. It doesn’t run an SPA build or use upload-code-site.

Local checks verify files and references, not how the site looks or behaves in design studio. After deploying to your test environment, review the site in your browser and design studio. Use /test-site to check the deployed site.

Improve your site without rebuilding

Add an information page, improve navigation, or refresh your branding without rewriting your site as an SPA. For new sites, start with a supported template and adapt it to your needs. Choose the approach that fits your project: an SPA framework or Power Pages web templates and Liquid code.

Get started

Before you begin, install Node.js long-term support (LTS), Microsoft Power Platform CLI, and Azure CLI. Then install the Power Pages plugin in GitHub Copilot CLI or Claude Code:

/plugin marketplace add microsoft/power-platform-skills
/plugin install power-pages@power-platform-skills

Important

Already have the plugin installed? Update it to the latest version (version 3.0.0 or later) to get support for sites using web templates and Liquid. In GitHub Copilot CLI, run:

copilot plugin update power-pages@power-platform-skills

To create a site, sign in to your target Power Platform environment. Ask an administrator to confirm that Switch to enhanced data model is enabled.

• Create a site: Run /create-site and ask for a site using web templates and Liquid, or choose a supported template labeled Non-SPA.
• Edit a site: Download its content with pac pages download, specifying its verified data model. Open the downloaded project and run /edit-site.

For setup details and supported workflows, see the Power Pages plugin documentation.

The post Create and edit non-SPA Power Pages sites with Agentic Coding tools appeared first on Microsoft Power Platform Blog.