@salesforce/templates 66.13.5 → 66.13.7

package/lib/templates/project/reactexternalapp/PRD.md

@@ -0,0 +1,38 @@
+# External User App (B2X)
+
+## Overview
+
+A ready-to-use starter for building customer- and partner-facing apps on the Salesforce platform. It comes with a clean, modern interface, a complete sign-in experience (login, registration, password reset, and profile management), and the public site setup needed to make the app available to people outside your company. It ships with no data of its own — a clean slate — but includes one working example (an Account search with filtering, sorting, and a detail view) that shows how the app reads Salesforce data, so teams can point it at their own information.
+
+## Problem
+
+Building a customer-facing portal on Salesforce usually means solving the hard parts before any real product work begins: letting people sign in and manage their accounts, keeping public and private areas properly separated, and configuring the public site so it can be served to external users. Getting sign-in right is especially important and easy to get wrong. Until now there has been no simple starting point that gets these pieces right from day one alongside a working example of showing Salesforce data.
+
+## Solution
+
+A minimal external-facing starter with everything already in place: the app framework, a full sign-in experience with protected private areas, a built-in Agentforce chat assistant, the public site setup, and a single example feature — Account search — that shows how the app displays Salesforce data. The sign-in and site setup are done for you so teams can focus on the customer experience, and the Account example serves as a template for building their own features.
+
+### Core Features
+
+- **Sign-in experience** — Login, registration, forgot/reset password, profile, and change-password screens, plus automatic sign-out after a period of inactivity.
+- **Public and private areas** — Public pages stay open to anyone, while signed-in areas are protected — the right default for a public site.
+- **Public site setup** — The site configuration needed to make the app available to external users out of the box.
+- **App framework and navigation** — A ready-made layout with a Home page and a "page not found" screen, prepared for adding new screens.
+- **Consistent design system** — A preinstalled set of interface building blocks so new screens look consistent from the start.
+- **Account search example** — A complete example with a search bar, filters, sorting, and paging, plus a search results screen and a detail view. This is the template for showing Salesforce data.
+- **Add-on features** — Tooling to browse and add additional prebuilt features into the app.
+
+### Non-Goals
+
+- Shipping a prebuilt data model — this starter deliberately includes none; teams bring their own.
+- Setting up single sign-on or an outside identity provider — it uses Salesforce's built-in sign-in for external sites.
+- A finished application — the Account example is meant to be copied and then removed, not kept.
+- Internal, employee-facing tools — use the Internal User App (B2E) starter for those.
+
+## Target Users
+
+Salesforce teams building customer- or partner-facing portals (self-service portals, order and status lookups, community front-ends) who want sign-in, access control, and the public site setup handled correctly from the start rather than assembled by hand.
+
+## Org prerequisites
+
+- Serving the app to external users requires **Experience Cloud (Digital Experiences)** to be enabled in the org, so the public site can be published.

package/lib/templates/project/reactexternalapp/README.md

@@ -96,9 +96,12 @@ Two npm scripts at the project root streamline getting started and deployment.
 
 **`npm run sf-project-setup`** — installs the UI Bundle dependencies, builds the app, and starts the dev server (see [Getting started](#getting-started)).
 
-**`npm run setup`** — runs the full deployment setup in one command: org login (if needed), UI Bundle build, deploy metadata, fetch GraphQL schema, run codegen, and optionally start the dev server:
+**`npm run setup`** — runs the full deployment setup in one command: org login (a required precondition, auto-skipped if already connected), UI Bundle build, deploy metadata, fetch GraphQL schema, and run codegen. It no longer starts the dev server — run `npm run dev:preview` for that:
 
 ```bash
+# Install project dependencies first (required before running setup)
+npm install
+
 npm run setup -- --target-org <alias>
 ```
 
@@ -110,15 +113,16 @@ npm run setup -- --target-org <alias> --yes
 
 Common options:
 
-| Option                    | Description                                    |
-| ------------------------- | ---------------------------------------------- |
-| `--skip-login`            | Skip browser login (org already authenticated) |
-| `--skip-deploy`           | Do not deploy metadata                         |
-| `--skip-graphql`          | Skip GraphQL schema fetch and codegen          |
-| `--skip-ui-bundle-build`  | Skip `npm install` and UI Bundle build         |
-| `--skip-dev`              | Do not start the dev server at the end         |
-| `--ui-bundle-name <name>` | UI Bundle folder name when multiple exist      |
-| `-y, --yes`               | Skip interactive step picker; run all steps    |
+| Option                    | Description                                     |
+| ------------------------- | ----------------------------------------------- |
+| `--target-org <alias>`    | Target org. If omitted, uses default org/prompt |
+| `--skip-deploy`           | Do not deploy metadata                          |
+| `--skip-graphql`          | Skip GraphQL schema fetch and codegen           |
+| `--skip-ui-bundle-build`  | Skip `npm install` and UI Bundle build          |
+| `--ui-bundle-name <name>` | UI Bundle folder name when multiple exist       |
+| `-y, --yes`               | Skip interactive step picker; run all steps     |
+
+> Login is a required precondition (no `--skip-login`), and the dev server is no longer part of setup (no `--skip-dev`); both flags are accepted but ignored. To start the dev server after setup, run `npm run dev:preview`.
 
 For all options: `npm run setup -- --help`.
 

package/lib/templates/project/reactexternalapp/_p_/_m_/_ps_/reactexternalapp_Guest_User_Api_Access.permissionset-meta.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
+    <hasActivationRequired>false</hasActivationRequired>
+    <label>reactexternalapp Guest User API Access</label>
+    <userPermissions>
+        <enabled>true</enabled>
+        <name>ApiEnabled</name>
+    </userPermissions>
+    <classAccesses>
+        <apexClass>UIBundleLogin</apexClass>
+        <enabled>true</enabled>
+    </classAccesses>
+    <classAccesses>
+        <apexClass>UIBundleForgotPassword</apexClass>
+        <enabled>true</enabled>
+    </classAccesses>
+    <classAccesses>
+        <apexClass>UIBundleRegistration</apexClass>
+        <enabled>true</enabled>
+    </classAccesses>
+    <classAccesses>
+        <apexClass>UIBundleSocialLoginConfig</apexClass>
+        <enabled>true</enabled>
+    </classAccesses>
+</PermissionSet>