@vit-foundation/ui 0.24.1 → 0.25.0

package/dist/content/pages.d.ts

@@ -0,0 +1,64 @@
+import type { EditDescriptor } from '../edit/types.js';
+/**
+ * Page copy: the editorial blocks of a static page, stored per page and
+ * section key in the website's `page_content` table. This module is the
+ * only declaration of which keys each page has — the website's `seed.sql`
+ * supplies their text and its repository integration test asserts the two
+ * agree, so a renamed or dropped row fails that suite instead of silently
+ * rendering nothing. vit-brain's `page-copy-keys.test.ts` pins the same set
+ * against the live table from the other side.
+ *
+ * It lived in fndvit-website's `schemas/page-copy.ts` and was restated in
+ * vit-brain's `mirror.ts` (with the FORMAT each block edits in — that half
+ * stays in brain, ADR-0019). Now that the page modules render from this
+ * package, the keys a page reads are the package's fact: a module indexes
+ * `copy.hero_title`, so the tuple that makes that compile has to live beside
+ * it. Component-free on purpose — `./contract` re-exports it for a host's
+ * `+page.server.ts` and a CMS's producer alike.
+ *
+ * UI chrome (labels, buttons, error messages) is not page copy: it lives in
+ * `UiMessages` and ships with the build.
+ */
+/**
+ * The "why get in touch" blocks, rendered as one list on /get-involved.
+ *
+ * Named because a run of keys being a *group* is a fact about the copy, and it
+ * needs the same single owner the keys themselves have: the page used to
+ * restate these five, so adding a sixth reason here and to the seed left the
+ * page silently ignoring it — no type error, no failing test.
+ */
+export declare const GET_INVOLVED_REASON_KEYS: readonly ["reason_collaborate", "reason_event", "reason_press", "reason_brand", "reason_other"];
+export declare const PAGE_COPY_KEYS: {
+    readonly home: readonly ["hero_title", "hero_subtitle", "milestones_heading", "weeklies_heading", "weeklies_intro", "know_more_heading"];
+    readonly 'what-we-do': readonly ["latest_heading", "collaborations_heading", "collaborations_intro", "passion_heading", "passion_intro"];
+    readonly 'who-we-are': readonly ["team_heading", "team_intro", "board_heading", "board_intro", "collaborators_heading"];
+    readonly weeklies: readonly ["intro"];
+    readonly 'get-involved': readonly ["contact_heading", "contact_intro", "reason_collaborate", "reason_event", "reason_press", "reason_brand", "reason_other", "funding_heading", "funding_body", "careers_heading", "careers_intro"];
+    readonly transparency: readonly ["heading", "intro"];
+    readonly legal: readonly ["heading", "body"];
+};
+/** A page that has editorial copy. Matches the `page_content.page` column. */
+export type PageId = keyof typeof PAGE_COPY_KEYS;
+/** The section keys declared for one page. */
+export type CopyKey<P extends PageId> = (typeof PAGE_COPY_KEYS)[P][number];
+/**
+ * One page's copy, one locale already applied. Every declared key is present:
+ * a row missing from the database resolves to an empty string rather than
+ * `undefined`.
+ *
+ * The page modules do NOT guard for that empty string. It is not a state the
+ * site is meant to render around — the website's repository integration test
+ * asserts that every declared key resolves to non-empty copy, so a dropped or
+ * renamed row fails the suite. Guarding at the render site instead puts the
+ * decision back at every call site, which is what the assertion exists to
+ * avoid (the same answer `CopyIntro` gives).
+ */
+export type PageCopy<P extends PageId> = Record<CopyKey<P>, string>;
+/**
+ * How a page module asks for one copy block's edit descriptor: by the key it
+ * renders, so a module cannot name a block its page does not declare. A
+ * read-only host passes nothing; a CMS answers with a `page-copy` ref for the
+ * locale being edited (vit-brain's `pageCopyEditor`), or `undefined` to leave
+ * one block alone.
+ */
+export type CopyEditFor<P extends PageId> = (key: CopyKey<P>) => EditDescriptor | undefined;

package/dist/content/pages.js

@@ -0,0 +1,71 @@
+/**
+ * Page copy: the editorial blocks of a static page, stored per page and
+ * section key in the website's `page_content` table. This module is the
+ * only declaration of which keys each page has — the website's `seed.sql`
+ * supplies their text and its repository integration test asserts the two
+ * agree, so a renamed or dropped row fails that suite instead of silently
+ * rendering nothing. vit-brain's `page-copy-keys.test.ts` pins the same set
+ * against the live table from the other side.
+ *
+ * It lived in fndvit-website's `schemas/page-copy.ts` and was restated in
+ * vit-brain's `mirror.ts` (with the FORMAT each block edits in — that half
+ * stays in brain, ADR-0019). Now that the page modules render from this
+ * package, the keys a page reads are the package's fact: a module indexes
+ * `copy.hero_title`, so the tuple that makes that compile has to live beside
+ * it. Component-free on purpose — `./contract` re-exports it for a host's
+ * `+page.server.ts` and a CMS's producer alike.
+ *
+ * UI chrome (labels, buttons, error messages) is not page copy: it lives in
+ * `UiMessages` and ships with the build.
+ */
+/**
+ * The "why get in touch" blocks, rendered as one list on /get-involved.
+ *
+ * Named because a run of keys being a *group* is a fact about the copy, and it
+ * needs the same single owner the keys themselves have: the page used to
+ * restate these five, so adding a sixth reason here and to the seed left the
+ * page silently ignoring it — no type error, no failing test.
+ */
+export const GET_INVOLVED_REASON_KEYS = [
+    'reason_collaborate',
+    'reason_event',
+    'reason_press',
+    'reason_brand',
+    'reason_other'
+];
+export const PAGE_COPY_KEYS = {
+    home: [
+        'hero_title',
+        'hero_subtitle',
+        'milestones_heading',
+        'weeklies_heading',
+        'weeklies_intro',
+        'know_more_heading'
+    ],
+    'what-we-do': [
+        'latest_heading',
+        'collaborations_heading',
+        'collaborations_intro',
+        'passion_heading',
+        'passion_intro'
+    ],
+    'who-we-are': [
+        'team_heading',
+        'team_intro',
+        'board_heading',
+        'board_intro',
+        'collaborators_heading'
+    ],
+    weeklies: ['intro'],
+    'get-involved': [
+        'contact_heading',
+        'contact_intro',
+        ...GET_INVOLVED_REASON_KEYS,
+        'funding_heading',
+        'funding_body',
+        'careers_heading',
+        'careers_intro'
+    ],
+    transparency: ['heading', 'intro'],
+    legal: ['heading', 'body']
+};

package/dist/content/types.d.ts

@@ -3,6 +3,7 @@
  * applied. The website's zod-inferred types satisfy these structurally; the
  * package states them itself so consumers owe it no schema library.
  */
+import type { EditDescriptor } from '../edit/types.js';
 /** The bounds of one form field; Field turns them into length attributes. */
 export interface FieldConstraint {
     min?: number;
@@ -28,6 +29,26 @@ export interface WeeklyCardData {
     excerpt: string;
     imageUrl: string;
 }
+/** A theme a weekly is filed under, as the /weeklies filter chips render it. */
+export interface ThemeData {
+    slug: string;
+    name: string;
+}
+/** One cited source of a weekly. */
+export interface WeeklySourceData {
+    label: string;
+    url: string;
+}
+/**
+ * A weekly's OWN page: the card, plus what only the detail renders. The
+ * website's `weeklyDetailSchema` carries `related` too; the page module
+ * takes that list as its own prop, because vit-brain loads it separately.
+ */
+export interface WeeklyArticleData extends WeeklyCardData {
+    body: string | null;
+    instagramUrl: string | null;
+    sources: WeeklySourceData[];
+}
 /** The kinds a project can have, in display order — a host's enum derives from this. */
 export declare const PROJECT_KINDS: readonly ["collaboration", "passion"];
 export type ProjectKind = (typeof PROJECT_KINDS)[number];
@@ -45,6 +66,28 @@ export interface ProjectCardData {
     externalUrl: string | null;
     hasStory: boolean;
 }
+/**
+ * A project's OWN page: the card, plus what only the detail renders. The
+ * website's `projectDetailSchema` and vit-brain's `toProjectArticle` both
+ * answer this shape.
+ */
+export interface ProjectArticleData extends ProjectCardData {
+    body: string | null;
+    previewImageUrl: string | null;
+}
+/**
+ * A weekly's or a project's OWN page: the same localized fields as its card,
+ * except that `body` renders as rich text there. Which surface a field is
+ * rendered on is the page's fact, and these two are the only pages with one
+ * — so the map is shared by `ProjectPage` and `WeeklyPage` and answered by
+ * one producer (vit-brain's `articleEdit`). All members optional, like every
+ * `*EditMap`: a host may open the body and leave the title alone.
+ */
+export interface ArticleEdit {
+    title?: EditDescriptor;
+    excerpt?: EditDescriptor;
+    body?: EditDescriptor;
+}
 /**
  * The timeline's categories, in DISPLAY ORDER — every select that offers them
  * and every host enum derives from this.
@@ -75,6 +118,8 @@ export interface MilestoneData {
     linkUrl: string | null;
 }
 export interface TeamMemberData {
+    /** Present only where the card is editable — a descriptor needs the row (precedent: CollaboratorData). */
+    id?: string | number;
     slug: string;
     name: string;
     role: string;

package/dist/content/types.js

@@ -1,8 +1,3 @@
-/**
- * Structural shapes of the content the components render, one locale already
- * applied. The website's zod-inferred types satisfy these structurally; the
- * package states them itself so consumers owe it no schema library.
- */
 /** The kinds a project can have, in display order — a host's enum derives from this. */
 export const PROJECT_KINDS = ['collaboration', 'passion'];
 /**

package/dist/content-components.d.ts

@@ -17,6 +17,24 @@ export { default as TimelineMilestone } from './components/timeline/TimelineMile
 export type { MilestoneEditMap } from './components/timeline/TimelineMilestone.svelte';
 export { default as WeeklieCard } from './components/weeklies/WeeklieCard.svelte';
 export type { WeeklyEditMap } from './components/weeklies/WeeklieCard.svelte';
+export { default as HomePage } from './components/pages/HomePage.svelte';
+export type { HomePageEdit } from './components/pages/HomePage.svelte';
+export { default as WhoWeArePage } from './components/pages/WhoWeArePage.svelte';
+export type { WhoWeArePageEdit } from './components/pages/WhoWeArePage.svelte';
+export { default as WhatWeDoPage } from './components/pages/WhatWeDoPage.svelte';
+export type { WhatWeDoPageEdit } from './components/pages/WhatWeDoPage.svelte';
+export { default as GetInvolvedPage } from './components/pages/GetInvolvedPage.svelte';
+export type { GetInvolvedPageEdit } from './components/pages/GetInvolvedPage.svelte';
+export { default as TransparencyPage } from './components/pages/TransparencyPage.svelte';
+export type { TransparencyPageEdit } from './components/pages/TransparencyPage.svelte';
+export { default as LegalPage } from './components/pages/LegalPage.svelte';
+export type { LegalPageEdit } from './components/pages/LegalPage.svelte';
+export { default as WeekliesPage } from './components/pages/WeekliesPage.svelte';
+export type { WeekliesPageEdit } from './components/pages/WeekliesPage.svelte';
+export { default as ProjectPage } from './components/pages/ProjectPage.svelte';
+export type { ProjectPageEdit } from './components/pages/ProjectPage.svelte';
+export { default as WeeklyPage } from './components/pages/WeeklyPage.svelte';
+export type { WeeklyPageEdit } from './components/pages/WeeklyPage.svelte';
 export * from './content/index.js';
 export { MILESTONE_CATEGORY_COLOR, matchesMilestoneFilter, milestoneCategoryLabel } from './utils/milestones.js';
 export { createUrlFilters } from './utils/url-filters.svelte.js';

package/dist/content-components.js

@@ -11,6 +11,18 @@ export { default as TeamMemberCard } from './components/team/TeamMemberCard.svel
 export { default as Timeline } from './components/timeline/Timeline.svelte';
 export { default as TimelineMilestone } from './components/timeline/TimelineMilestone.svelte';
 export { default as WeeklieCard } from './components/weeklies/WeeklieCard.svelte';
+// The nine PAGE modules: a website route is one tag over the site's read
+// projection, and a CMS opens it with the module's `*PageEdit` map. Same door
+// as the cards they compose — a page is content that renders, not chrome.
+export { default as HomePage } from './components/pages/HomePage.svelte';
+export { default as WhoWeArePage } from './components/pages/WhoWeArePage.svelte';
+export { default as WhatWeDoPage } from './components/pages/WhatWeDoPage.svelte';
+export { default as GetInvolvedPage } from './components/pages/GetInvolvedPage.svelte';
+export { default as TransparencyPage } from './components/pages/TransparencyPage.svelte';
+export { default as LegalPage } from './components/pages/LegalPage.svelte';
+export { default as WeekliesPage } from './components/pages/WeekliesPage.svelte';
+export { default as ProjectPage } from './components/pages/ProjectPage.svelte';
+export { default as WeeklyPage } from './components/pages/WeeklyPage.svelte';
 export * from './content/index.js';
 export { MILESTONE_CATEGORY_COLOR, matchesMilestoneFilter, milestoneCategoryLabel } from './utils/milestones.js';
 // The two list rules: URL-mirrored filters, and the weeklies index over them.

package/dist/contract.d.ts

@@ -47,6 +47,9 @@ export { MILESTONE_CATEGORIES, PROJECT_KINDS } from './content/types.js';
 export type { MilestoneCategory, ProjectKind } from './content/types.js';
 export { WEEKLY_LIST_DEFAULTS, WEEKLY_LIST_PARAMS, parseWeeklyListUrl } from './utils/weekly-list-contract.js';
 export type { WeeklyListFilters, WeeklyListPage, WeeklyListServerData } from './utils/weekly-list-contract.js';
+export { GET_INVOLVED_REASON_KEYS, PAGE_COPY_KEYS } from './content/pages.js';
+export type { CopyEditFor, CopyKey, PageCopy, PageId } from './content/pages.js';
+export type { ArticleEdit, ProjectArticleData, ThemeData, WeeklyArticleData, WeeklySourceData } from './content/types.js';
 export { CONTACT_CATEGORIES } from './content/types.js';
 export { COMMENT_STATUSES } from './content/types.js';
 export type { CommentStatus, ContactCategory, FieldConstraint, FormFailReason } from './content/types.js';

package/dist/contract.js

@@ -49,6 +49,10 @@ export { MILESTONE_CATEGORIES, PROJECT_KINDS } from './content/types.js';
 // half had three spellings across two repositories and this package's own test,
 // and the round-trip case guarding them crossed against the test's copy.
 export { WEEKLY_LIST_DEFAULTS, WEEKLY_LIST_PARAMS, parseWeeklyListUrl } from './utils/weekly-list-contract.js';
+// The page-copy vocabulary: which blocks each static page reads. A host's
+// `+page.server.ts` builds `PageCopy<P>` from it and a CMS's producer binds
+// its own per-page format table to it, both on the server.
+export { GET_INVOLVED_REASON_KEYS, PAGE_COPY_KEYS } from './content/pages.js';
 export { CONTACT_CATEGORIES } from './content/types.js';
 export { COMMENT_STATUSES } from './content/types.js';
 export { COMMENT_BODY, CONTACT_MESSAGE, CONTACT_NAME, DISPLAY_NAME, EMAIL, LOGIN_PASSWORD, PASSWORD } from './forms/constraints.js';

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vit-foundation/ui",
-	"version": "0.24.1",
+	"version": "0.25.0",
 	"scripts": {
 		"dev": "vite dev",
 		"build": "vite build && npm run prepack",