Organisms
01
Page band
The black band at the top of the main box: the page title and its tabs.
- The section's name, one or two words: "Design system", "Narrator".
- When there are tabs: the route of the page shown, so its tab gets the dot.
- When the page sits inside a list: the list's route, drawn as a chevron before the title.
- Centres the tabs in the band, the title at the left and
toggleat the right: the back office's tools, a client's tabs.
- Component
PageBandView(default)- Import
@/app/components/PageBandViewin apps/app- What it is
- The sticky black band atop the main box: a back chevron when the page sits inside a list, the page title, its tabs after the title or centred, a control at the far end.
- Use when
- The band when its title and tabs are known: the page band draws it from the URL, the design system from samples, a client page itself, having the client's name.
- Never
- A second band on a page, since the layout draws it; a fill other than black, since its tabs are white on it (§8).
| Prop | Type | Use it for | Never |
|---|---|---|---|
| title | string · required | The section's name, one or two words: "Design system", "Narrator". | A sentence. |
| tabs | PageBandTab[] · required | The section's sub-pages in order: name the label, href its route. Empty for a section with none. | |
| currentHref | string | When there are tabs: the route of the page shown, so its tab gets the dot. | |
| back | string | When the page sits inside a list: the list's route, drawn as a chevron before the title. | |
| centred | boolean · default false | Centres the tabs in the band, the title at the left and toggle at the right: the back office's tools, a client's tabs. | |
| toggle | ReactNode | When the page has a view switch, or Sign out: the control at the far end of the band. | A second control, since the band has one end. |
- Example
<PageBandView title="Design system" tabs={[ { name: "Atoms", href: "/design-system/atoms" }, { name: "Molecules", href: "/design-system/molecules" }, ]} currentHref="/design-system/molecules" />
import PageBandView from "@/app/components/PageBandView";
<PageBandView title="Design system" tabs={[
{ name: "Atoms", href: "/design-system/atoms" },
{ name: "Molecules", href: "/design-system/molecules" },
]} currentHref="/design-system/molecules" />02
Side nav
The app's navigation, a row on a phone and a column from 767px.
- Component
SideNavView(default)- Import
@/app/components/SideNavViewin apps/app- What it is
- The app's sections as icon and label links, the current one trailed by the orange dot: a row on a phone, a 176px column from 767px.
- Use when
- The nav when its items are known. The app's side nav draws it from the URL, the design system from
navItems. - Never
- A second nav on a page, since the layout draws it; a rule or a box around it, since only the main box is framed (§8).
| Prop | Type | Use it for | Never |
|---|---|---|---|
| items | Item[] · required | The app's sections as navItems lists them: name the label, href its route, icon its name in the set, external for another app. | |
| currentHref | string | When a page is shown: the route it owns, so its item gets the dot. |
- Example
<SideNavView items={navItems} currentHref="/design-system" />
import SideNavView from "@/app/components/SideNavView";
<SideNavView items={navItems} currentHref="/design-system" />03
Site navbar and footer
The top and bottom of www.bprigent.com.
- Component
Navbar(default)- Import
@/app/components/site/Navbar- What it is
- The sticky site header: the logo, the Blog, About and Apps links as plain text, and the hiring link as a
TextLinkDieterat the end. - Use when
- Placed once, in layout.tsx.
- Never
- A second one on a page, since the layout places it; its links restyled, since they are plain text by design (§7).
No props.
- Example
<Navbar />
import Navbar from "@/app/components/site/Navbar";
<Navbar />- Component
Footer(default)- Import
@/app/components/site/Footer- What it is
- Fetches. The site's foot: the "Still Hiring" circle, the social links, the page links in columns, and the title of every article.
- Use when
- Placed once, in layout.tsx.
- Never
- A second one on a page, since the layout places it; a rule between its columns, since space separates them (§8).
- Deviates
- Bottom padding on its call-to-action section (§5) and a box around the whole footer (§8); reuse them, do not copy either.
No props.
- Example
<Footer />
import Footer from "@/app/components/site/Footer";
<Footer />04
Site sections
The sections www pages are built from: hero, header, about, two-column text, the three text-and-image layouts, the dot globe and the blog hero.
- Component
SectionHero- Import
@/app/components/ui/section-hero- What it is
- The opening of a page: an
H1on the left and a shortPSmalllabel on the right, in the page's grid. - Use when
- Opening a page with a title and a short aside.
/aboutplaces one, under its image. - Never
- Twice on a page, since it holds the
<h1>; a long label, which is a paragraph.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string · required | The page's one title, one sentence: the about page's line on design as a business tool. | A second sentence. |
| label | React.ReactNode · required | A short aside beside the title, plain text or JSX with a <br />: a name and a role. | A paragraph, since it is a label. |
- Example
<SectionHero heading="I’m a product designer who treats design as a business tool: for revenue, leverage, and long-term market power." label="Benjamin Prigent, Product Design Lead" />
import { SectionHero } from "@/app/components/ui/section-hero";
<SectionHero
heading="I’m a product designer who treats design as a business tool: for revenue, leverage, and long-term market power."
label="Benjamin Prigent, Product Design Lead"
/>- Component
SectionHeader- Import
@/app/components/ui/section-header- What it is
- The opening of a page as an eyebrow and a title: a
PSmalllabel above anH1, in one column. - Use when
- Opening a page with a short line over its title.
/opens with one. - Never
- Twice on a page, since it holds the
<h1>; withSectionHeroon the same page, which holds one too. - Deviates
- Bottom padding (§5); reuse it, do not copy it.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| label | string · required | One line over the title: who speaks, or where the reader is: "Hello, I am Benjamin Prigent, …". | A second sentence. |
| heading | string · required | The page's one title, one sentence. | A second sentence. |
- Example
<SectionHeader label="Hello, I am Benjamin Prigent, product design lead at Pigment." heading="I build cash-positive digital products that help people reach their goals." />
import { SectionHeader } from "@/app/components/ui/section-header";
<SectionHeader
label="Hello, I am Benjamin Prigent, product design lead at Pigment."
heading="I build cash-positive digital products that help people reach their goals."
/>- Component
SectionAbout- Import
@/app/components/ui/section-about- What it is
- A label and content section: an
H2with aPSmallsubheading and, from 767px, the circle call to action on the left; twoPparagraphs on the right, the circle under them on a phone. - Use when
- An introduction in two paragraphs with one action.
/places one. - Never
- Without
linkHrefandlinkText, since it draws an empty circle; a second one on a page, since a page spends the orange once (§1). - Deviates
- Bottom padding (§5); reuse it, do not copy it.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string · required | The section's name, one to three words: "About me". | A sentence. |
| subheading | string · required | One line under the heading, in dark grey: a role or a summary. | |
| textBlock1 | string · required | The first paragraph, three to five sentences. | |
| textBlock2 | string · required | The second paragraph, three to five sentences. | |
| linkHref | string | When the section has an action: the route the circle opens, /about. Set with linkText. | Left out, since the circle draws empty. |
| linkText | string | When the section has an action: the circle's text, one to three words, "Learn more". Set with linkHref. | Left out, since the circle draws empty. |
- Example
<SectionAbout heading="About me" subheading="Designer and product builder" textBlock1="I’m currently a Product Design Lead at Pigment where I work on AI agents for financial planning. My main value add comes from business experience, I approach design as a tool for revenue and leverage, and I tend to think in terms of systems." textBlock2="Before Pigment, I founded two companies. I sold one early; the other I ran for two and a half years before shutting it down. After that, I joined a venture studio to learn how to structure innovation more deliberately. Later, I spent three years at Meta, where I learned what building at scale really means, and how systems, process, and organization shape outcomes." linkHref="/about" linkText="Learn more" />
import { SectionAbout } from "@/app/components/ui/section-about";
<SectionAbout
heading="About me"
subheading="Designer and product builder"
textBlock1="I’m currently a Product Design Lead at Pigment where I work on AI agents for financial planning. My main value add comes from business experience, I approach design as a tool for revenue and leverage, and I tend to think in terms of systems."
textBlock2="Before Pigment, I founded two companies. I sold one early; the other I ran for two and a half years before shutting it down. After that, I joined a venture studio to learn how to structure innovation more deliberately. Later, I spent three years at Meta, where I learned what building at scale really means, and how systems, process, and organization shape outcomes."
linkHref="/about"
linkText="Learn more"
/>- Component
Section2ColumnText- Import
@/app/components/ui/section-2-column-text- What it is
- An
H2across the top, then two columns side by side from 767px, 6/6 from 991px, each anH3over its paragraphs. - Use when
- Two parallel lists of principles or points under one heading.
/aboutplaces one. - Never
- Columns of unequal weight, which is a text-and-image section; more than five paragraphs a column, which is an article.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string · required | The section's name, a few words or one sentence: "What I believe about building products". | |
| leftH3 | string · required | The left column's title, two or three words: "Product principles". | |
| leftParagraphs | string[] · required | One paragraph each, two to five, each opening with its point in one sentence. | |
| rightH3 | string · required | The right column's title, two or three words: "Execution principles". | |
| rightParagraphs | string[] · required | One paragraph each, two to five, as many as the left. |
- Example
<Section2ColumnText heading="What I believe about building products" leftH3="Product principles" leftParagraphs={[ "Design must account for both the problem and the goal: User problems matter, but solving symptoms without understanding the underlying goal leads to local optimizations and global failure. I care as much about why a problem exists as how it manifests.", "More choices equals less action. People don’t like comparing options; they like clear answers. Reducing choices is often the fastest way to unlock movement.", ]} rightH3="Execution principles" rightParagraphs={[ "Today, not one day. Vision is easy, in my opinion. The hard part is deciding what single outcome matters today. Progress is about outcomes, not output.", "Only good passes. Work only matters if it can be handed off in a way others can act on. If it can’t be used, it’s not finished.", ]} />
import { Section2ColumnText } from "@/app/components/ui/section-2-column-text";
<Section2ColumnText
heading="What I believe about building products"
leftH3="Product principles"
leftParagraphs={[
"Design must account for both the problem and the goal: User problems matter, but solving symptoms without understanding the underlying goal leads to local optimizations and global failure. I care as much about why a problem exists as how it manifests.",
"More choices equals less action. People don’t like comparing options; they like clear answers. Reducing choices is often the fastest way to unlock movement.",
]}
rightH3="Execution principles"
rightParagraphs={[
"Today, not one day. Vision is easy, in my opinion. The hard part is deciding what single outcome matters today. Progress is about outcomes, not output.",
"Only good passes. Work only matters if it can be handed off in a way others can act on. If it can’t be used, it’s not finished.",
]}
/>- Component
SectionTextAndImage1- Import
@/app/components/ui/section-text-and-image-1- What it is
- An
H2across the top, then the paragraphs on the left and a square image on the right, 4/4 from 767px, 6/6 from 991px, the caption over the image's bottom-left corner. - Use when
- Text with an image beside it, image right, 6/6. One of three layouts of one idea: pick by layout, not by name.
/aboutplaces one. - Never
- A tall image, since the frame is square; an empty
imageAlt, since a missing alt is a defect (§9). - Deviates
- A hairline around the image (§8); reuse it, do not copy it.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string · required | The section's name, a few words: "What I work on today". | |
| paragraphs | string[] · required | One paragraph each, one to four. | |
| imageSrc | string · required | The image's path under public/. | |
| imageAlt | string · required | What the image shows, one sentence (§9). | Empty (§9). |
| imageCaption | string | When the image needs a line: what or where it is, over its bottom-left corner: "Pigment Platform". |
- Example
<SectionTextAndImage1 heading="What I work on today" paragraphs={[ "Today I’m a Product Design Lead at Pigment, where we build AI agents for the world of EPM and FP&A. Alongside design, I code often. It keeps me close to the product, and it makes me a better collaborator with engineers.", "Outside of my day job, I take on a small amount of freelance work: building websites and running digital ads, mostly for people around me in my local community (I live in a small town in Bretagne).", ]} imageSrc="/images/about-pigment.avif" imageAlt="image of pigment interface" imageCaption="Pigment Platform" />
import { SectionTextAndImage1 } from "@/app/components/ui/section-text-and-image-1";
<SectionTextAndImage1
heading="What I work on today"
paragraphs={[
"Today I’m a Product Design Lead at Pigment, where we build AI agents for the world of EPM and FP&A. Alongside design, I code often. It keeps me close to the product, and it makes me a better collaborator with engineers.",
"Outside of my day job, I take on a small amount of freelance work: building websites and running digital ads, mostly for people around me in my local community (I live in a small town in Bretagne).",
]}
imageSrc="/images/about-pigment.avif"
imageAlt="image of pigment interface"
imageCaption="Pigment Platform"
/>- Component
SectionTextAndImageLeft- Import
@/app/components/ui/section-text-and-image-left- What it is
- A label and content layout: the
H2and the image under it in the left column, the paragraphs on the right, 5/7 from 991px, the caption in white over the image's corner. - Use when
- Text with an image under its heading, 5/7. One of three layouts of one idea: pick by layout, not by name.
/aboutplaces one. - Never
- A wide image, since the column is narrow; an empty
imageAlt, since a missing alt is a defect (§9). - Deviates
- A rule around the image (§8); reuse it, do not copy it.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string · required | The section's name, a few words: "Building from 0 to 1". | |
| imageSrc | string · required | The image's path under public/. | |
| imageAlt | string · required | What the image shows, one sentence (§9). | Empty (§9). |
| imageCaption | string | When the image needs a line: what or where it is, in white over its corner: "2016, Ease, France". | |
| paragraphs | string[] · required | One paragraph each, one to four. |
- Example
<SectionTextAndImageLeft heading="Building from 0 to 1" imageSrc="/images/about-ease.jpg" imageAlt="ease team when we were young" imageCaption="2016, Ease, France" paragraphs={[ "I started building companies during university. The first was a small hardware refurbishment and repair business. We worked with tight margins and real operational constraints. A year after creation, we were selling the business to a competitor for a small profit.", "Across all these experiences, an operating principle progressively emerged. The product designer’s role is not fixed, it changes depending on what the team is trying to validate: a problem, a value proposition, a feature, a business model, or a growth mechanism.", ]} />
import { SectionTextAndImageLeft } from "@/app/components/ui/section-text-and-image-left";
<SectionTextAndImageLeft
heading="Building from 0 to 1"
imageSrc="/images/about-ease.jpg"
imageAlt="ease team when we were young"
imageCaption="2016, Ease, France"
paragraphs={[
"I started building companies during university. The first was a small hardware refurbishment and repair business. We worked with tight margins and real operational constraints. A year after creation, we were selling the business to a competitor for a small profit.",
"Across all these experiences, an operating principle progressively emerged. The product designer’s role is not fixed, it changes depending on what the team is trying to validate: a problem, a value proposition, a feature, a business model, or a growth mechanism.",
]}
/>- Component
SectionImageLeftTextRight- Import
@/app/components/ui/section-image-left-text-right- What it is
- An
H2across the top, then the image on the left and short dark greyPSmallparagraphs on the right, 8/4 from 991px, the caption in white over the image's corner. - Use when
- A dominant image with a short side note, 8/4. One of three layouts of one idea: pick by layout, not by name.
/aboutplaces one. - Never
- Long text, since the column is narrow and its type small; an empty
altinimage, since a missing alt is a defect (§9). - Deviates
- Bottom padding (§5) and a rule around the image (§8); reuse them, do not copy either.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string · required | The section's name, a few words: "Immersing in different cultures". | |
| image | { src: string; alt: string; caption?: string } · required | src the path under public/, alt what it shows (§9), caption a line in white over its corner when it needs one. | An empty alt (§9). |
| paragraphs | string[] · required | One paragraph each, one to five, short. |
- Example
<SectionImageLeftTextRight heading="Immersing in different cultures" image={{ src: "/images/about-fun-1.jpeg", alt: "Air baloon over the desert, Jordan", caption: "Jordan" }} paragraphs={[ "Between the ages of 15 and 30, I spent close to nine years living abroad. I lived in the United States, Cambodia, South Korea, Switzerland, and later Canada.", "All in all, it reinforced a simple idea: people are rarely the problem, systems are.", ]} />
import { SectionImageLeftTextRight } from "@/app/components/ui/section-image-left-text-right";
<SectionImageLeftTextRight
heading="Immersing in different cultures"
image={{ src: "/images/about-fun-1.jpeg", alt: "Air baloon over the desert, Jordan", caption: "Jordan" }}
paragraphs={[
"Between the ages of 15 and 30, I spent close to nine years living abroad. I lived in the United States, Cambodia, South Korea, Switzerland, and later Canada.",
"All in all, it reinforced a simple idea: people are rarely the problem, systems are.",
]}
/>- Component
SectionDotGlobe- Import
@/app/components/ui/section-dot-globe- What it is
- Client. A globe of dots the reader can drag, drifting when idle, an
H2above it. Under it, a previous and a next chevron step through past positions, the active one named between them with its place and years. - Use when
- The about page's map of past positions.
/aboutplaces one. - Never
- Twice on a page, since a second globe is a second animation; a small
maxSize, which hides the positions.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string | When the globe needs a title: the section's name: "Where I have worked". | |
| dotCount | number · default 5000 | How many dots make the sphere. More is denser and slower to draw. | |
| maxSize | number · default 520 | The globe's largest diameter in pixels. It never exceeds its column. |
- Example
<SectionDotGlobe heading="Where I have worked" />
import { SectionDotGlobe } from "@/app/components/ui/section-dot-globe";
<SectionDotGlobe heading="Where I have worked" />- Component
BlogHero- Import
@/app/components/ui/blog-hero- What it is
- Fetches. The latest article under a "Latest article" label: its
H1title, intro, date and "Read it" circle on the left, ruled above and below, its cover on the right; the cover above on a phone. - Use when
- The top of the blog, after its banner.
/blogplaces one. - Never
- On the home, where
SectionBlogteases the blog; twice on a page, since it holds the<h1>. - Deviates
- Rules above and below its text column (§8); reuse them, do not copy them.
No props.
- Example
<BlogHero />
import { BlogHero } from "@/app/components/ui/blog-hero";
<BlogHero />05
Lists
Entries separated by space and alignment, never by rules. The blog list is the reference.
- Component
SectionBlog- Import
@/app/components/ui/section-blog- What it is
- Fetches. A label and content section: an
H2with a fixedPSmallline on the left, the three latest articles asListEntrys and the "All articles" circle on the right. - Use when
- The home page's teaser of the blog.
/places one. - Never
- On
/blog, which lists everything withAllArticles; twice on a page, since it spends the orange (§1). - Deviates
- Bottom padding (§5); reuse it, do not copy it.
No props.
- Example
<SectionBlog />
import { SectionBlog } from "@/app/components/ui/section-blog";
<SectionBlog />- Component
PinnedPosts- Import
@/app/components/ui/pinned-posts- What it is
- Fetches. Up to three pinned articles under a "Pinned articles" label, one card each: a square thumbnail, the title clamped at two lines, the date.
- Use when
- Under the blog's hero.
/blogplaces one. - Never
- As the article list, which is
AllArticles; a card restyled with a box, since a card gets no box (§8).
No props.
- Example
<PinnedPosts />
import { PinnedPosts } from "@/app/components/ui/pinned-posts";
<PinnedPosts />- Component
AllArticles- Import
@/app/components/ui/all-articles- What it is
- Fetches. Every article but the latest and the pinned: an
H2"All other articles" on the left, a column ofListEntrys on the right, dates first, intros clamped. - Use when
- The full list of the blog.
/blogplaces one. - Never
- On the home, where
SectionBlogshows three; twice on a page, since it lists every article once.
No props.
- Example
<AllArticles />
import { AllArticles } from "@/app/components/ui/all-articles";
<AllArticles />06
Tables
The home page's logo table, the older ruled kind: one rule above, one below. A data table is the Table molecule.
- Component
SectionWork- Import
@/app/components/ui/section-work- What it is
- A label and content section: an
H2on the left, a table ofWorkRows on the right, one rule above and one below (§8). - Use when
- A ruled table of names and logos, the site's reference table.
/places one. - Never
- Rules between rows, since a table rules once above and once below (§8).
- Deviates
- Bottom padding (§5); reuse it, do not copy it.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| heading | string · required | The table's name: "Previous work". | |
| items | WorkItem[] · required | One per row, six today, in order: label what was done, svgPath the logo, alt the client, svgHeight its height in pixels. | An item without alt (§9). |
- Example
<SectionWork heading="Previous work" items={[ { label: "AI Agents for FP&A", svgPath: "/clients/Pigment.svg", alt: "Pigment", svgHeight: 14 }, { label: "Ad products, Browser, and AI", svgPath: "/clients/Meta.svg", alt: "Meta", svgHeight: 16 }, { label: "IOT, Mobile, E-Commerce", svgPath: "/clients/Colgate.svg", alt: "Colgate", svgHeight: 12 }, { label: "E-commerce, Supply chain", svgPath: "/clients/Kraft.svg", alt: "Kraft", svgHeight: 16 }, { label: "Online payment", svgPath: "/clients/Audi.svg", alt: "Audi", svgHeight: 20 }, { label: "Internal operations", svgPath: "/clients/Richemont.svg", alt: "Richemont", svgHeight: 12 }, ]} />
import { SectionWork } from "@/app/components/ui/section-work";
<SectionWork
heading="Previous work"
items={[
{ label: "AI Agents for FP&A", svgPath: "/clients/Pigment.svg", alt: "Pigment", svgHeight: 14 },
{ label: "Ad products, Browser, and AI", svgPath: "/clients/Meta.svg", alt: "Meta", svgHeight: 16 },
{ label: "IOT, Mobile, E-Commerce", svgPath: "/clients/Colgate.svg", alt: "Colgate", svgHeight: 12 },
{ label: "E-commerce, Supply chain", svgPath: "/clients/Kraft.svg", alt: "Kraft", svgHeight: 16 },
{ label: "Online payment", svgPath: "/clients/Audi.svg", alt: "Audi", svgHeight: 20 },
{ label: "Internal operations", svgPath: "/clients/Richemont.svg", alt: "Richemont", svgHeight: 12 },
]}
/>07
Component preview
How this page shows every component: the sample on a checkerboard, then its props, its agent.md record and its code behind a bar of tabs, and its name to copy.
<Button type="button" primary>Copy JSON</Button>- Component
ComponentPreview(default)- Import
@/app/components/ComponentPreviewin apps/app- What it is
- Client. How the design system shows one thing: the sample on a checkerboard, ruled in grey, then a bar of text tabs on the code panel's fill, each opening its panel below, and the name with a copy icon.
- Use when
- Every entry on the design system's tabs.
/design-systemplaces one per entry. - Never
- A page outside the design system, since it is how the design system shows a thing; a sample with a box of its own, since the preview frames it.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| name | string | When the sample is one component: its name, shown in the bar and copied by its icon. | |
| panels | PreviewPanel[] · required | One per tab in order: label the tab's text, content the panel, rendered by the caller so a server page fills it. | |
| defaultPanel | number | null · default 0 | Which panel starts open, by index. null starts with every panel closed. |
- Children
ReactNode· required. The sample as the app draws it: one component, or a few that belong together. Never: a sample with a box of its own, since the preview frames it; a whole page.
- Example
<ComponentPreview name="Button" panels={[{ label: "Code", content: <Code code={code} /> }]}> <Button type="button" primary>Copy JSON</Button> </ComponentPreview>
import ComponentPreview from "@/app/components/ComponentPreview";
<ComponentPreview name="Button" panels={[{ label: "Code", content: <Code code={code} /> }]}>
<Button type="button" primary>Copy JSON</Button>
</ComponentPreview>08
Forms
Fields stacked with the one action at the end, like the sign-in.
- Component
Form(default)- Import
@/app/components/Formin apps/app- What it is
- Fields stacked
horizontal-padding-paragraphapart, the one actionhorizontal-padding-headingbelow the last. A hidden input takes no row. - Use when
- Any form in apps/app.
/loginand/backoffice/clientsplace one. - Never
- A second action inside it, since a form has one (§8); a box or a rule around it, since a rule marks a section (§8); a
<form>with its own spacing in apps/app, which is this one.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| action | (formData: FormData) => void | Promise<void> | When the form submits with its fields filled: the server action that receives them. Left out only by the design system's sample. | |
| submit | ReactNode · required | The one Button, primary, under the fields: "Sign in", "Save". | Two buttons, since a form has one action (§8). |
| columns | 1 | 2 · default 1 | 1 stacks the fields. 2 sets them side by side from 767px, for short fields in pairs. | |
| className | string | Width or space around the <form>: max-w-[400px]. | A box or a rule (§8). |
- Children
ReactNode· required. The fields asFields, a hidden input where the action needs one, and an error line among them when the last submit failed. Never: the submit, which issubmit; a<fieldset>with a box (§8).
- Example
<Form submit={<Button type="submit" primary>Sign in</Button>} action={signIn}> <Field label="Email"> <Input type="email" name="email" /> </Field> <Field label="Password"> <Input type="password" name="password" /> </Field> </Form>
import Form from "@/app/components/Form";
<Form submit={<Button type="submit" primary>Sign in</Button>} action={signIn}>
<Field label="Email">
<Input type="email" name="email" />
</Field>
<Field label="Password">
<Input type="password" name="password" />
</Field>
</Form>09
Article parts
The hero, the block body and the FAQ that every article is made of.
- Component
ArticleHero- Import
@/app/components/site/article-hero- What it is
- Fetches. The article named by
slug: itsH1, intro and published date in white over the cover, which sits under a light dark layer. - Use when
- The top of an article page, after its banner.
/article/<slug>places one. - Never
- Elsewhere on the page, since it holds the
<h1>.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| slug | string · required | The article's slug column, from the route: open-source-ai-budgeting-app-claude-cod. |
- Example
<ArticleHero slug="open-source-ai-budgeting-app-claude-cod" />
import { ArticleHero } from "@/app/components/site/article-hero";
<ArticleHero slug="open-source-ai-budgeting-app-claude-cod" />- Component
ArticleBody- Import
@/app/components/site/article-body- What it is
- The article's blocks in a centred column 800px wide: headings, paragraphs, images, code and embeds in the document's order.
- Use when
- The body of an article page, under its hero.
/article/<slug>places one. - Never
- With content that has not passed
articleContent.ts, since one bad block 404s the page.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| content | ArticleContent · required | The block document, validated by articleContent.ts from the row's content JSON. | The raw JSON string. |
- Example
<ArticleBody content={[{ type: "heading", props: { level: 2, text: "How an article reaches the blog", id: "how-an-article-reaches-the-blog" } }]} />
import { ArticleBody } from "@/app/components/site/article-body";
<ArticleBody content={[{ type: "heading", props: { level: 2, text: "How an article reaches the blog", id: "how-an-article-reaches-the-blog" } }]} />- Component
ArticleFaq- Import
@/app/components/site/article-faq- What it is
- A list of
<details>: anH2, then each question as anH3with a plus that turns to a minus, the answer under it. Draws nothing when empty. - Use when
- An article's FAQ, after the body.
/article/<slug>places one. - Never
- A FAQ written into the body as paragraphs, which a reader cannot fold.
- Deviates
- A box around each item (§8); reuse it, do not copy it.
| Prop | Type | Use it for | Never |
|---|---|---|---|
| items | FaqItem[] | string | null | undefined · required | The row's faq: { question, answer } items, or that list as a JSON string, which it parses. null or empty draws nothing. | Markdown in an answer, which prints as text. |
| topic | string · required | The article's h1, which nothing reads today. |
- Example
<ArticleFaq topic="I built an AI-first open-source budgeting app" items={[ { question: "Is bud-a really free, or does it require a paid subscription?", answer: "Bud-a itself is free and open-source. You do need an active Claude Code subscription to run the AI agents (receipt parsing, spending analysis, backups). If you already use Claude Code for development or other projects, there's no additional cost for bud-a.", }, { question: "How does Bud-a compare to Actual Budget?", answer: "They serve different needs. Actual Budget is better for households that want bank sync, envelope budgeting methodology, and multi-device sync across machines. Bud-a is for households that want AI in the loop: receipt parsing from photos, natural-language spending analysis, and Telegram-based mobile input.", }, ]} />
import { ArticleFaq } from "@/app/components/site/article-faq";
<ArticleFaq
topic="I built an AI-first open-source budgeting app"
items={[
{
question: "Is bud-a really free, or does it require a paid subscription?",
answer: "Bud-a itself is free and open-source. You do need an active Claude Code subscription to run the AI agents (receipt parsing, spending analysis, backups). If you already use Claude Code for development or other projects, there's no additional cost for bud-a.",
},
{
question: "How does Bud-a compare to Actual Budget?",
answer: "They serve different needs. Actual Budget is better for households that want bank sync, envelope budgeting methodology, and multi-device sync across machines. Bud-a is for households that want AI in the loop: receipt parsing from photos, natural-language spending analysis, and Telegram-based mobile input.",
},
]}
/>