@sevenfold/setto-client 0.12.1 → 0.13.0

package/dist/admin/App.d.ts

@@ -1,11 +1,16 @@
 /**
- * Drop-in admin SPA. Mount under a route like `<Route path="/setto/*" .../>`.
+ * The page at `/setto`. Mount it under a route like `<Route path="/setto/*" …>`.
  *
- * Behaviour after login:
- *  - Redirects to the site home `/`. Edit mode activates automatically there
- *    via `SettoProvider` when the user has access to `config.siteId`.
- *  - Shows the dashboard only when the user lacks access to this site, or
- *    when a panel was asked for: `/setto?deployment=…` for publish progress
- *    and history, `/setto?view=<module>` for a module's panel (forms today).
+ * What draws it lives in setto-server now, not here. The chrome bundle offers a
+ * dashboard at runtime — publish history, the forms inbox, the domain panel —
+ * and that is what fills this route, so changing any of it is one deploy of
+ * Setto rather than a rebuild of every site it has ever made.
+ *
+ * What stays behind is the door: sign in, and get back to the site to edit.
+ * That much has to work from the site's own bundle, because it is the only way
+ * in and because the bug that takes the chrome down could be mine. Everything
+ * past the door is Setto's, needs Setto to be reachable to do anything at all,
+ * and is better absent than drawn from a copy that has been quietly rotting in
+ * a pinned version since the day the site was built.
  */
 export declare function SettoAdminApp(): import("react/jsx-runtime").JSX.Element;

package/dist/modules/domain/index.d.ts

@@ -6,6 +6,8 @@ import type { SettoModule } from '../module';
  * setting somebody returns to — when they finally buy the name, when they move
  * registrar, when a record gets deleted by accident — and the conversation
  * that built the site is not somewhere anybody goes back to.
+ *
+ * Only the tab is here. The panel behind it is served from setto-server, which
+ * is also where the DNS instructions are worked out.
  */
 export declare const domainModule: SettoModule;
-export { DomainView } from './DomainView';

package/dist/modules/forms/index.d.ts

@@ -1,8 +1,8 @@
 import type { SettoModule } from '../module';
 /**
- * The forms module: a form primitive the site renders, an inbox in the
- * dashboard, and the api segment between them. Server side lives in
- * setto-server `src/modules/forms`.
+ * The forms module: a form primitive the site renders, and the api segment
+ * behind it. Server side lives in setto-server `src/modules/forms`, and so
+ * does the inbox the customer reads submissions in.
  */
 export declare const formsModule: SettoModule;
 export { SettoForm } from './SettoForm';

package/dist/modules/index.d.ts

@@ -1,5 +1,5 @@
 import type { SettoModule } from './module';
 export type { SettoModule } from './module';
-/** Every module the dashboard shows, in tab order. */
+/** Every module the dashboard shows, in tab order. Setto draws the tabs. */
 export declare const SETTO_MODULES: readonly SettoModule[];
 export declare function findModule(id: string | null): SettoModule | undefined;

package/dist/modules/module.d.ts

@@ -1,30 +1,26 @@
-import type { ComponentType } from 'react';
 /**
  * What a Setto module is, from the client's side.
  *
  * A module is a capability a site gets by using the library — forms today;
  * bookings, newsletters, reviews later. Each one is a directory under
- * `src/modules/<id>` that owns its three faces:
+ * `src/modules/<id>` that owns the two faces the customer's own bundle has to
+ * carry:
  *
  *   - a primitive the site renders (`SettoForm`), with edit chrome for the
  *     owner and content that lives in the locale so it publishes with the
  *     rest of the site;
- *   - a panel in the dashboard at `/setto?view=<id>` (`AdminView`), reached
- *     from the editor toolbar's settings item;
  *   - an api segment (`createFormsApi`) that `createApi` mounts under its id,
  *     against routes setto-server keeps under `src/modules/<id>`.
  *
- * Registering the module in `src/modules/index.ts` is what puts its tab in
- * the dashboard. The primitive and the types are exported from the package
- * root like everything else.
+ * The third face — the panel at `/setto?view=<id>` — is not here. It lives in
+ * setto-server under `chrome/src/admin/modules`, and arrives at runtime, so a
+ * new module's panel ships in a deploy instead of a rebuild of every site.
+ * What this list is still for is the editor toolbar, which links to those
+ * panels from the customer's page and needs their ids and labels to do it.
  */
 export interface SettoModule {
     /** Stable id — also the dashboard view name and the api segment name. */
     id: string;
     /** Tab label in the dashboard, in Norwegian. */
     label: string;
-    /** The dashboard panel for the current site. */
-    AdminView: ComponentType<{
-        siteId: string;
-    }>;
 }