Elements
The Agento design system
Colours, type, components, and every page section in the theme, with the names you need to reuse them.
Colours
- Brand
brandGradient end, links - Brand 2
brand-2Gradient start - Brand soft
brand-softTints, chips - Ink
inkHeadings - Ink 2
ink-2Strong body - Muted
mutedBody text - Subtle
subtleLabels, meta - Line
lineBorders - Line 2
line-2Inner dividers - Canvas
canvasPage background - Surface
surfaceCards - Surface 2
surface-2Insets - Success
accent-greenStatus: done - Purple
accent-purpleGlows - Orange
accent-orangeAccents - Brand gradient
from-brand-2 to-brandNever a solid brand fill
Typography
- Display · Instrument SerifHand off the busywork
- Heading · Instrument SerifAgents that work inside your tools
- Title · Geist 600Approvals that scale
- Body · Geist 400Agents research, decide, and act inside the apps your team already uses.
- Label · Geist 600, uppercaseSection label
Shadows and radii
shadow-cardshadow-float
rounded-xl · tilesrounded-2xl · inner cardsrounded-3xl · cardsrounded-4xl · panels
Form fields
Please enter a valid email address.
Chips and badges
- New
- Improved
- Needs approval
- Blocked
- Neutral
Icons
botworkflowchartsearchmailcalendardatabaseshielduser-lockflashtargetheadsetcoinscodelayersbookglobekeylockeyeplugsparklescheckarrow-right
Sections 114
Every section in src/components/sections, with its description and the pages that use it. The list is generated at build time.
AboutHeroAbout page hero: the mission as a very large serif statement over a soft glow, a short intro, and a row of quick facts.
Used on/about
AboutStoryCompany story as a growth chart: one panel, a column per year split by hairlines.
Used on/about
AboutTeamTeam grid: portrait (soft zoom on hover), name, role, and profile links.
Used on/about
AboutValuesValues: four columns between hairlines, each with a numbered label, an icon, a title, and a short line. No cards.
Used on/about
AccessMatrixSplit layout: heading and points on the left; a permissions matrix (agents × scopes) on the right.
Used on/security
AffiliateCalculatorEarnings calculator.
Used on/affiliates
AffiliateHeroAffiliate hero: headline, text, points, and the join button on the left; the commission rate as a large gradient figure on a card on the right.
Used on/affiliates
AffiliateStepsHow the affiliate program works: three numbered steps joined by a hairline.
Used on/affiliates
ApiAuthAuthentication and limits: the three security points on the left; the rate-limit table and a link to the full reference on the right.
Used on/api
ApiFeaturesApiQuickstartAPI quickstart: heading, tabbed code (cURL, JavaScript, Python), and the official SDKs as cards with their install command.
Used on/api
AuthorHeroAuthor archive header: breadcrumbs, the author's photo, name, role, bio, profile links, and post count.
Used on/blog/author/[author]
BeforeAfterBefore and after: each row sets the same job without Agento against the benefit with Agento.
Used on/product/[slug]/solutions/[slug]
BenefitsGridThree (or more) benefits in columns separated by hairlines, under a section heading. No card framing.
Used on/security
BlogIndexBlog index and category archives: category tabs (links), the featured post on page one, the post grid, and pagination.
Used on/blog/blog/author/[author]/blog/category/[category]/blog/tag/[tag]
CapabilityListSplit layout: a left-aligned heading on the left (sticky on desktop), a two-column list of capabilities on the right.
Used on/product/[slug]
CareersBenefitsWhy work here: benefit cards in a three-column grid.
Used on/careers
CareersPhotosCulture photos as a bento: the first photo large, two squares beside it, and a wide one below them. Two columns on phones.
Used on/careers
CareersRolesOpen roles grouped by team, each a row linking to its post.
Used on/careers
CaseStudiesCustomer stories: one featured story (quote, photo, and a before → after time line) beside two smaller cards that each lead with a single result. Every card links to its full story page. Stories come from the `customers` content collection; the first by `order` is featured. Cards fade up once as they scroll in.
Used on/
ChangelogTeaserThe latest changelog releases as rows: date, version, title, and tags, each linking to its entry.
Used on/home-2
ChangelogTimelineChangelog timeline, newest first, grouped by month.
Used on/changelog
ClientsClient logos in two slow marquee rows (the first half of the list on top, the rest below), fading at the edges.
Used on/
ComingSoonComing soon: section label, serif headline, a live countdown to `launch` (tiles), and an email capture with a success line.
Used on/coming-soon
ComparisonTablePlan comparison: grouped rows, one column per plan.
Used on/pricing
ContactOfficesOffice locations as three columns between hairlines: city in serif, country, address, and hours.
Used on/contact
ContactSectionContact form in a card, with direct contact options (sales, support, press) beside it. Demo submits go to /thank-you.
Used on/contact
CtaCtaBannerClosing banner for inner pages.
Used on/about/affiliates/api/careers/contact/customers/customers/[slug]/enterprise/help/integrations/integrations/[slug]/pricing/product/product/[slug]/security/showcase/solutions/solutions/[slug]/templates/templates/[slug]/use-cases/use-cases/[slug]
CustomerFeaturedThe featured customer story on /customers.
Used on/customers/solutions
CustomerGridGrid of customer story cards.
Used on/customers/customers/[slug]
DataTableA simple three-column table under a section heading (e.g. sub-processors). Hairline rows, no card.
Used on/security
DeveloperSectionFor developers: text and three points on the left; a dark code panel with tabs on the right.
Used on/product
DevHeroDocsArticleA docs page.
Used on/docs
DocsLinksDocs quick links: the first docs pages as cards (section, title, description), with a link to all docs.
Used on/home-2
ElementsGuideStyle guide.
Used on/elements
EnterpriseDeploymentDeployment options: three cards; the featured one (e.g. VPC) is raised with a gradient ring and a badge.
Used on/enterprise
EnterpriseGovernanceGovernance controls: a 3×2 grid between hairlines (no cards), each with an icon, title, text, and small tags.
Used on/enterprise
EnterpriseHeroEnterprise hero: pitch, three proof points, and client logos on the left; the "talk to sales" form card on the right.
Used on/enterprise
EnterpriseSupportSupport and SLA tiers: a comparison table (rows × tiers) with the featured tier highlighted. Scrolls sideways on phones.
Used on/enterprise
FaqFAQ: a split layout. The heading and a support block (team photos, status, actions) stay pinned on the left (desktop) while the questions scroll on the right. The open question lifts into a soft card and the straight inset hairlines around it (drawn with ::after) fade away. Native <details>, so it works without JavaScript; open/close is animated where the browser supports animating ::details-content (see global.css).
Used on/
FaqGridQuestions and answers laid out in two columns, all visible (no accordion). For inner pages.
Used on/affiliates/contact/enterprise/pricing/request-access/security/solutions/[slug]
FeatureGridThe product features as a platform map.
Used on/product/[slug]
FeatureRowsScroll-driven feature tour. Desktop: the steps scroll in the left column while a sticky stage on the right swaps scenes. A rail runs exactly from the first dot to the last and fills as you scroll; each dot activates (with a small pop) the moment the fill reaches it, and that step becomes current. Phones: no sticky stage; each step shows its own scene inline. State lives in `data-current` / `data-reached` attributes and CSS variables, set by the script below.
Used on/
GettingStartedTime to value: four numbered steps across a hairline grid, each with how long it takes .
Used on/product
GovernanceCalloutGoverned by default.
Used on/product
HelpArticleA help article.
Used on/help/[slug]
HelpHeroHelp center hero: big serif question, a large search pill (opens the search palette over every article), and popular quick links.
Used on/help
HelpTopicsHelp topics as tiles (icon, name, line, article count, and the first articles), then popular articles as a list.
Used on/help
HeroHome hero: the serif headline and actions over the dotted field, with the live agent demo (prompt, current task, workflow, and activity feed).
Used on/
HowItWorksHow it works: three steps (describe, connect, execute), each with its own small product visual, joined by the brand mark.
Used on/
IntegrationHeroIntegration hero.
Used on/integrations/[slug]
IntegrationRelatedRelated integrations under an app page: a heading and up to four app cards.
Used on/integrations/[slug]
IntegrationsIntegrations, laid out on the page itself (no framing box): heading on top, then app cards on both sides joined to the Agento hub by lines in each app's colour (drawn by the script below from the live layout), sparkle dots behind the hub, and a footer with the stat, category chips that filter the apps, and a link to the directory. Phones and tablets: hub, cards in a grid, footer; no lines.
IntegrationsDirectoryIntegrations directory.
Used on/integrations
IntegrationSetupSetup and permissions side by side.
Used on/integrations/[slug]
IntegrationUsesWhat you can automate with an app: numbered cards, each with a title and a line of detail.
Used on/integrations/[slug]
JobPostA job post.
Used on/careers/[slug]
LegalDocumentOne legal document.
Used on/legal/[slug]
LegalListLegal hub: every legal document as a row between hairlines, with its summary, last-updated date, and an arrow.
Used on/legal
MaintenanceMaintenance: section label, serif headline, a card with the expected return time and the upgrade's progress steps, then status and support links.
Used on/maintenance
MetricsChart geometry in percentages.
Used on/
NewsletterNewsletter sign-up (blog, changelog).
Used on/blog/blog/[slug]/blog/author/[author]/blog/category/[category]/blog/tag/[tag]/changelog/resources/status
NotFoundOnboardingFlowOnboarding as one card with steps: role → team size → tools → first template → done.
Used on/onboarding
PartnerApplyPartner application: pitch and points on the left, the application form (with a success state) on the right.
Used on/partners
PartnerDirectoryPartner directory: program chips (with counts) above partner cards with logo, program, region, and a line.
Used on/partners
PartnerTiersPartner programs: three cards; the featured one is raised with a gradient border and a badge.
Used on/partners
PlatformDiagramThe platform as a left-to-right flow.
Used on/product
PostBodyBlog post body.
Used on/blog/[slug]
PostHeaderBlog post header: breadcrumbs (blog → category), the h1, the summary, author, date, reading time, and the cover.
Used on/blog/[slug]
PostRelatedRelated posts under a blog post: a heading and up to three post cards.
Used on/blog/[slug]
PricingPricing: three plan cards in a row. The featured plan sits in a brand-gradient frame with a "Most popular" strip on top and a soft brand wash inside; the others align with its inner card. A segmented toggle (and the "pay yearly" link under each price) switches billing; the script updates every price.
PricingUsageUsage and add-ons.
Used on/pricing
QuoteBandOne customer quote, large and centred, with the author's photo and company.
Used on/enterprise/product/product/[slug]/request-access/solutions/[slug]/templates/[slug]/use-cases/[slug]
RequestAccessRequest access, the whole page above the fold.
Used on/request-access
RequestStepsWhat happens after a request: numbered steps laid out on the page (no box), each with when it happens.
Used on/request-access
ResourceCardsTwo side-by-side action cards (e.g. request a report, report a vulnerability).
Used on/security
ResourceHubResources hub.
Used on/resources
RunTimelineOne task, shown through the work it produces.
Used on/product
SecuritySecurity: the one dark band on the page, composed around the product itself. A centred heading, then the live audit log as the centrepiece (filter tabs, rows that slide in from the top, a stats strip), and the controls in a hairline-separated row beneath it.
Used on/
ShowcaseCoreShowcase core features: a grid of icon tiles with a label under each, set directly on the page.
Used on/showcase
ShowcaseDemosShowcase home demos.
Used on/showcase
ShowcaseHeroShowcase hero: an editorial split (headline left, pitch and stats right), then the first home demo in front of two inner pages.
Used on/showcase
ShowcasePagesShowcase inner pages: a framed stage on the soft surface holding a grid of page thumbnails, each with its group and title.
Used on/showcase
ShowcaseSupportShowcase support: support and documentation side by side, split by a hairline.
Used on/showcase
ShowcaseWhyShowcase "Why Agento": a bento of four cards, each with a product visual above its title.
Used on/showcase
SitemapIndexHTML sitemap: a jump bar of groups, then each group as a heading (icon, name, page count) over a multi-column link list.
Used on/sitemap
SolutionAgentsReady-made agents for a team.
Used on/solutions/[slug]/templates/[slug]
SolutionIndustriesSolutions by industry.
Used on/solutions
SolutionSceneHero visual for a solution page.
Used on/solutions/[slug]
SolutionSizesSolutions by company size: plain rows between hairlines, each linking to its page (Enterprise to /enterprise).
Used on/solutions
SolutionStatsThree headline results for a team, as large serif numbers between hairlines. No box: it reads as a band.
Used on/about/solutions/[slug]/use-cases/[slug]
SolutionTeamsSolutions by team.
Used on/solutions
SolutionWorkflowOne workflow, step by step, laid out on the page: nodes on a rail (horizontal on desktop, vertical on phones).
Used on/solutions/[slug]
StartupHeroStartup home (Home 3).
Used on/home-3
StatusBoardStatus page body.
Used on/status
StoryBodyThe full customer story: a sticky facts sidebar (industry, size, headquarters, team, connected apps) beside the Markdown body.
Used on/customers/[slug]
StoryCompareThe same week of work before and with Agento, from a customer story's `before` / `after` task lists.
Used on/customers/[slug]
TemplateFlowThe template's run as a vertical flow inside a framed stage: trigger → read → agent → (approval) → result.
Used on/templates/[slug]
TemplateGalleryTemplates gallery: a search field and team chips above a grid of template cards.
Used on/templates
TemplateHeroTemplate hero: breadcrumbs, the agent's icon tile, name and description, chips for when it runs and who uses it, and actions.
Used on/templates/[slug]
TemplateIOInputs, outputs, and the tools a template needs: two columns between hairlines, then the app tiles (linked to their integration pages).
Used on/templates/[slug]
ThankYouConfirmation after a form: a check mark, the h1 and message, three next steps, and a link home.
Used on/thank-you
TrustBadgesCompliance certifications as small audit certificates in one panel, split by hairlines.
Used on/enterprise/security
UseCaseGridUse cases grid with team filter chips (a small script hides cards that don't match).
Used on/use-cases
UseCaseProblemThe problem a use case solves, shown as the work it creates today.
Used on/use-cases/[slug]
UseCaseRelatedMore use cases: a heading and three use-case cards.
Used on/use-cases/[slug]
UseCaseRunOne agent run, step by step, in a framed stage.
Used on/use-cases/[slug]
UseCasesSource icons stacked in the research tile's footer.
Used on/
UseCaseTemplateThe template behind a use case: pitch on the left, the template card on the right (links to its page).
Used on/use-cases/[slug]
WaitlistWaitlist: centred hero with an email pill and social proof.
Used on/waitlist
WaitlistComingWhat's coming with the waitlisted product: three numbered cards.
Used on/waitlist