惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
V
V2EX
Jina AI
Jina AI
爱范儿
爱范儿
M
MIT News - Artificial intelligence
量子位
L
LangChain Blog
Google DeepMind News
Google DeepMind News
酷 壳 – CoolShell
酷 壳 – CoolShell
罗磊的独立博客
腾讯CDC
MongoDB | Blog
MongoDB | Blog
P
Proofpoint News Feed
宝玉的分享
宝玉的分享
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Last Week in AI
Last Week in AI
H
Hackread – Cybersecurity News, Data Breaches, AI and More
F
Fortinet All Blogs
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
博客园 - 聂微东
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Vercel News
Vercel News
T
The Blog of Author Tim Ferriss

Netlify Changelog

Gemini 3.5 Flash now available in Agent Runners 4 Nuxt CVEs: what Netlify users need to know Gemini 3.5 Flash now available in AI Gateway Agent Runners workflow improvements Next.js & React security release (May 2026): what to know Block project transfers out of your team Gemini 3.1 Flash-Lite now available in AI Gateway OpenAI GPT-5.5 Instant now available in AI Gateway New `netlify logs` CLI command Deploy to Netlify with Stripe Projects Netlify Database is now generally available OpenAI GPT-5.5 and GPT-5.5 Pro in AI Gateway & Agent Runners Rename an agent run GPT Image 2 now available in AI Gateway New frontend-design skill for Agent Runners Claude Opus 4.7 now available in AI Gateway and Agent Runners Pricing updates for Credit-based plans New sorting and filter controls on the Members page Netlify Database GA coming soon, no new databases for now Deploy logs streaming is now faster Netlify CLI adds prompt-based creation and anonymous deploys Deploy from Codex with the Netlify Plugin Hydrogen with React Router 7 now supported on Netlify Monitor credit usage by day Invoices for Enterprise Available on the Billing Page AI app development on production infrastructure with Netlify Introducing Prompt Templates OpenAI GPT-5.4 Nano and GPT-5.4 Mini in AI Gateway Change your pricing plan Internal Builder Role & Project Access Controls
Add a surface to extension UI
2025-01-31 · via Netlify Changelog

The extension UI boilerplate code includes an extension details page surface, which users will access under Extensions > [your extension’s details page] > Configuration in the Netlify UI. You can change this to a different surface or add additional ones for various locations in the Netlify UI.

This document covers how to update your extension UI to add an additional surface to render in the Netlify UI. It also includes a list of available surfaces and their configuration values for your reference.

For more information about all of the components and surfaces available, refer to the extension UI reference docs.

Add a new surface

Section titled “Add a new surface”

  1. First, edit the extension’s configuration file (extension.yaml) to add a new surface under surfaces.

    For example, to add the Project Notifications Configuration surface, add extension-site-notifications-configuration.

    config:

    ui:

    surfaces:

    - extension-team-configuration

    - extension-site-notifications-configuration

    This signals to the Netlify UI that it should show your extension UI when a user installs your extension and navigates to Project configuration > Notifications.

  2. Next, create the new component that Netlify should render for this surface in the Netlify UI. For example, add new file called SiteNotificationsConfiguration.tsx under src/ui/surfaces/ with the following component code:

    import {

    Card,

    CardTitle,

    Form,

    FormField,

    FormFieldSecret,

    SiteNotificationsConfigurationSurface,

    } from "@netlify/sdk/ui/react/components";

    export const SiteNotificationsConfiguration = () => {

    const onSubmit = (values) => {

    // Do something with form values

    };

    return (

    <SiteNotificationsConfigurationSurface>

    <Card>

    <Form onSubmit={onSubmit}>

    <FormField name="username" label="Username" />

    <FormFieldSecret name="password" label="password" />

    <Select

    name="notification_provider"

    label="Notification Provider"

    options={[

    { label: "SMS", value: "SMS" },

    { label: "Email", value: "email" },

    { label: "Carrier Pigeon", value: "carrier_pigeon" },

    ]}

    />

    </Form>

    </Card>

    </SiteNotificationsConfigurationSurface>

    );

    };

  3. Next, update the extension UI application to render your new component when a user navigates to the correct surface:

    import { Surfaces } from "@netlify/sdk/ui/react";

    import { SurfaceRouter, SurfaceRoute } from "@netlify/sdk/ui/react/components";

    import { TeamConfiguration } from "./surfaces/TeamConfiguration.jsx";

    import { SiteNotificationsConfiguration } from "./surfaces/SiteNotificationsConfiguration.jsx";

    export const App = () => (

    <SurfaceRouter>

    <SurfaceRoute surface={Surfaces.TeamConfiguration}>

    <TeamConfiguration />

    <SurfaceRoute>

    <SurfaceRoute surface={Surfaces.SiteNotificationsConfiguration}>

    <SiteNotificationsConfiguration />

    <SurfaceRoute>

    </SurfaceRouter>

    );

  4. Next, redeploy the extension so that you can preview it locally. Redeploying and updating your private extension is only required when you add or remove surfaces.

  5. Now, you can run start local development. Once the server starts, navigate to Project configuration > Notifications for your project in the Netlify UI and the new surface should appear. The original boilerplate surface should also still appear when you navigate to Team settings > General team settings

Available surfaces

Section titled “Available surfaces”

The Netlify SDK supports extension UI for the following surfaces across team sections and project sections of the Netlify UI.

For team features and configurations, you can add the following surfaces:

Extension details page

Section titled “Extension details page”

Note that this surface is sometimes referred to as the Team Configuration surface.

  • Location in the Netlify UI: Extensions > [your extension’s details page] > Configuration
  • Component name: TeamConfigurationSurface
  • Value for extension.yaml: extension-team-configuration

For project features and configurations, you can add the following surfaces:

General project settings

Section titled “General project settings”

  • Location in the Netlify UI: Project configuration > General
  • Component name: SiteGeneralConfigurationSurface
  • Value for extension.yaml: extension-site-general-configuration

Project access & security settings

Section titled “Project access & security settings”

  • Location in the Netlify UI: Project configuration > Access & security
  • Component name: SiteAccessConfigurationSurface
  • Value for extension.yaml: extension-site-access-configuration

Project build & deploy settings

Section titled “Project build & deploy settings”

  • Location in the Netlify UI: Project configuration > Build & deploy
  • Component name: SiteBuildDeployConfigurationSurface
  • Value for extension.yaml: extension-site-build-and-deploy-configuration

Project notification settings

Section titled “Project notification settings”

  • Location in the Netlify UI: Project configuration > Notifications
  • Component name: SiteNotificationsConfigurationSurface
  • Value for extension.yaml: extension-site-notifications-configuration

Top-level project section

Section titled “Top-level project section”

Note that this surface is sometimes referred to as the Top-Level Project Configuration surface.

  • Location in the Netlify UI: a section listed under the top-level navigation for projects.
  • Component name: SiteConfigurationSurface
  • Value for extension.yaml: extension-top-level-site-configuration

  • Location in the Netlify UI: Deploys > [your project deploy page]
  • Component name: SiteDeploySurface
  • Value for extension.yaml: extension-site-deploy

Now that you’ve created an extension, reviewed it in the Netlify UI, and added a new surface, you can create rich interactions by creating an endpoint and calling it from the UI.

For more information about all of the components and surfaces available, refer to the extension UI reference docs.