@rizom/brain 0.1.1-alpha.6 → 0.1.1-alpha.7

package/dist/seed-content/relay/README.md

@@ -322,7 +322,7 @@ Recall is built on a plugin-based architecture:
 
 This is an internal tool, but we welcome contributions:
 
-1. Follow the [CLAUDE.md](../../CLAUDE.md) development guidelines
+1. Follow the repository [AGENTS.md](../../AGENTS.md) development guidelines
 2. Write tests for new features
 3. Run `bun run typecheck` and `bun run lint` before committing
 4. Keep commits focused and write clear messages

package/dist/site.d.ts

@@ -11,8 +11,9 @@
  *
  * **Sync rules:**
  * - When the runtime shape of `SitePackage`, `personalSitePlugin`,
- *   `PersonalLayout`, or `routes` changes, this file MUST be updated
- *   in the same commit.
+ *   `professionalSitePlugin`, `PersonalLayout`, `ProfessionalLayout`,
+ *   or the route exports changes, this file MUST be updated in the
+ *   same commit.
  * - `Plugin` and `RouteDefinitionInput` are deliberately opaque
  *   pass-throughs — consumers receive them, hand them back, and
  *   never introspect. Do NOT expand them to mirror internal shapes.
@@ -39,8 +40,9 @@ import type { ComponentType } from "preact";
 
 /**
  * Opaque plugin marker. Consumers receive plugin instances via
- * `personalSitePlugin(config)` and pass them along to brain.yaml /
- * brain definitions; they do not introspect the shape themselves.
+ * `personalSitePlugin(config)` / `professionalSitePlugin(config)` and
+ * pass them along to brain.yaml / brain definitions; they do not
+ * introspect the shape themselves.
  */
 export interface Plugin {
   readonly id: string;
@@ -50,7 +52,7 @@ export interface Plugin {
 }
 
 /**
- * Opaque route definition. Consumers receive `routes` from
+ * Opaque route definition. Consumers receive route exports from
  * `@rizom/brain/site` and place them on the `SitePackage.routes`
  * field verbatim — they do not construct or modify the shape.
  */
@@ -86,9 +88,11 @@ export interface EntityDisplayEntry {
 }
 
 /**
- * A site package bundles everything the site-builder needs:
- * theme CSS, layout components, hand-written routes, the site
- * plugin factory, and per-entity display metadata.
+ * A site package bundles everything the site-builder needs for site
+ * structure: layout components, hand-written routes, the site plugin
+ * factory, and per-entity display metadata.
+ *
+ * Themes are resolved separately by the framework.
  *
  * @example
  * ```ts
@@ -98,10 +102,8 @@ export interface EntityDisplayEntry {
  *   routes,
  * } from "@rizom/brain/site";
  * import type { Plugin, SitePackage } from "@rizom/brain/site";
- * import themeCSS from "./theme.css" with { type: "text" };
  *
  * const site: SitePackage = {
- *   theme: themeCSS,
  *   layouts: { default: PersonalLayout },
  *   routes,
  *   plugin: (config) => personalSitePlugin(config ?? {}),
@@ -114,8 +116,6 @@ export interface EntityDisplayEntry {
  * ```
  */
 export interface SitePackage {
-  /** Composed theme CSS string */
-  theme: string;
   /** Layout components keyed by name — at minimum "default" is required */
   layouts: Record<string, unknown>;
   /** Hand-written route definitions */
@@ -147,3 +147,28 @@ export function personalSitePlugin(config?: Record<string, unknown>): Plugin;
  * (homepage, about, etc.). Place verbatim on `SitePackage.routes`.
  */
 export const routes: RouteDefinitionInput[];
+
+/**
+ * Alias for the personal site routes. Prefer this in new code when you
+ * want to be explicit about which layout family you are pairing.
+ */
+export const personalRoutes: RouteDefinitionInput[];
+
+/**
+ * Professional site layout — a Preact component used as the default
+ * layout in a `SitePackage.layouts` map for professional/editorial sites.
+ */
+export const ProfessionalLayout: ComponentType<Record<string, unknown>>;
+
+/**
+ * Professional site plugin factory. Registers templates, datasources,
+ * and schema extensions needed by the professional layout.
+ */
+export function professionalSitePlugin(
+  config?: Record<string, unknown>,
+): Plugin;
+
+/**
+ * Hand-written route definitions for the professional layout.
+ */
+export const professionalRoutes: RouteDefinitionInput[];