Gensudo
Gensudo

Shared foundations with explicit marketing and app guidance.

Overview

What the system is, how it works, and how to use the guide.

Overview

Foundations

Universal design rules that stay true across Gensudo surfaces.

FoundationsColoursGradientsTypographySpacingGrid & Layout

Surface Conventions

How marketing and app surfaces intentionally differ.

MarketingAppPatterns

System

Shared primitives, identity assets, and reference materials.

ComponentsButtonsFormsFeedback & OverlaysProgressTagsInteractive CardsSkeletonsLayout & ShellsMarketing PrimitivesNot Yet StandardizedAssetsLogoIconography

Governance

How changes are made without creating design drift.

GovernanceLegacy InventoryPromotion Path

Consumer surfaces

Marketing siteProduct app

Components

Live documentation backed by the shared UI package.

These examples import real components from `@gensudo/ui`. They exist to show sanctioned variants and surface expectations, not to recreate static screenshots.

Component catalog

Buttons

Shared button variants, sizes, and current guidance on what is not yet standardized.

Forms

Shared `Field` wrappers, inputs, selects, and auth-form framing available today.

Feedback & Overlays

Current banners, notices, and modal shells that exist in the shared UI package.

Progress

Shared progress bars for project cards, phase task tracking, and other completion states.

Tags

Shared compact labels for lightweight metadata, phase chips, and type markers.

Interactive Cards

Shared clickable and selectable card shells for app surfaces where the whole card is the action.

Skeletons

Shared loading placeholders for blocking states across page headers, cards, panels, and workspace layouts.

Layout & Shells

Page headers, section shells, toolbars, auth shells, and the shared app shell.

Marketing Primitives

Marketing hero, nav, feature cards, and pricing cards backed by the shared package.

Not Yet Standardized

Legacy-inspired patterns like toggles, icon-only buttons, and tables that are not shared truth yet.

Current rule

This catalog only documents what is real in the current shared system. If a legacy pattern does not exist in `packages/ui`, it should be marked as not yet standardized instead of being presented like a shared truth.