# Trim design system Trim helps small Filipino creators find deals they can earn from and share with their audiences. App teams can reward eligible signups or trials. Local shops can run visit-based offers and in-store promos. Customers can see the benefit, check the terms and know how to claim it. ## Brand direction Use the warmth of a neighborhood shop and the clarity of a well-set flyer. Cream paper, dark aubergine, large serif headlines and candid photographs give the editorial surfaces their character. Rounded ticket edges and simple concentric lines can frame a feature image, divide a section or mark a redemption card. Keep supporting motifs small enough that the offer, amount and action always read first. Write **Trim** in copy. Set headings and featured deal names in Fraunces at weight 700 with the expressive softness and wonk settings from the design tokens. Keep optical sizing automatic. Set navigation, controls, body copy, merchant names in dense lists and financial data in DM Sans. Use at least 16 px for visible text. Dedicated footer fine print can use 14 px. Use tabular figures for prices and payouts that people will compare in a column. Keep official business names as supplied and use semantic HTML headings to establish hierarchy. Use the [wordmark](assets/trim-wordmark.png) in headers and the [ticket mark](assets/trim-mark.png) where space is tight, such as a favicon. Both exports have a transparent background and use the light-surface brand colors. Keep the ticket at its original angle and give the mark room around its notches. | Role | Use | | --- | --- | | Cream canvas and paper | Cream for the main page. Warm white for forms, offer cards and detail panels. | | Plum ink and aubergine | Plum for text. Aubergine for primary actions and occasional full-width editorial surfaces paired with inverse text. | | Lilac, sage and ochre | Quiet surfaces for categories, examples and supporting callouts. Pair each surface with its assigned text token and keep the category name visible. | | Coral | A small focal accent in the brand. Use the alert tokens for warnings and errors so corrective messages have a consistent meaning. | | Rules and borders | Use subtle rules for layout and a stronger boundary when a control depends on its outline for recognition. | Use one column for narrow layouts and keep the offer amount, terms and main action together as a card expands. In wider layouts, align cards and financial rows to a shared grid. Favor comfortable line lengths for descriptions and help text. Use a consistent rounded stroke for interface icons and pair unfamiliar actions with visible labels. Keep decorative ticket edges and contour lines outside control boundaries. ## Voice and examples Speak plainly and name the action. Write for the person making the decision. Use sentence case, short verbs and pesos. State conditions where people decide whether to join, share or claim. Use urgency only when an actual deadline or limit applies. | Audience | What matters to them | Example copy | | --- | --- | --- | | Creator | Finding an offer their audience would use and knowing what earns a payout. | “Earn ₱80 for each approved trial.” | | Business | Choosing an action they can measure and controlling the cost. | “Set a reward for each verified store visit.” | | Customer | Seeing the saving, where to use it and any eligibility rules. | “Get ₱100 off orders over ₱500 at the Cubao branch.” | Use **offer** for the item a person can browse or share, **campaign** for the business setup, **reward** for the creator amount per qualifying action, and **payout** for money sent to a creator. Call the customer benefit **discount**, **promo**, or **trial**, according to the terms. Use **save** for bookmarking an offer, **claim** for receiving a code or securing a benefit, and **redeem** for applying it. Prefer labels that specify the outcome, such as “Join campaign,” “Copy offer link,” and “Show promo code.” Keep transactional copy in clear Philippine English. Use conversational Taglish in campaign headlines and captions when it fits the audience. Format PHP amounts with `Intl.NumberFormat` and show centavos whenever they are meaningful, such as on payout records. Use an abbreviated month name when a numeric date could be ambiguous, as in “18 Nov 2026.” Render time-sensitive deadlines in `Asia/Manila` and label them “Philippine time.” For store offers, list the eligible branch, city or municipality and applicable days or hours. ## Offer and account patterns | Pattern | Information and behavior | | --- | --- | | Offer card | Show the action category, offer title, brand and the audience's own amount or benefit. Surface a material limit or eligibility condition. Give the title or a clear link the navigation role, with Save as an independent toggle. Keep type labels such as “App trial” and “Store visit” visible alongside their category colors. | | App signup or trial | Show who qualifies, the completion step, verification window and creator reward. When relevant, show the customer's payment requirement, trial end and renewal terms before they start. | | Store visit or promo | Show the participating branch, time window, spend threshold and how to present the code or claim. Make the promo code readable as text and copyable. Pair any QR with an equivalent link or code. | | Campaign setup | Ask for one qualifying action, a reward per approved action, an eligibility window and a cap or budget if available. Show the business how those terms appear to a creator before publication. | | Progress | Put the current text status and the next action beside the offer or conversion. Use date-stamped steps for a longer process. Icons and colors reinforce the written state. | | Earnings summary | Use clearly titled values for estimated, approved and paid earnings where each is present. Show a payout's amount, date or expected timing, and reference when available. Keep earnings and customer savings separately labeled in any share preview or detail view. | | Empty and error state | Explain the specific result and give a retry or recovery action when available. “No store offers match these filters. Clear filters to see more.” A form error belongs beside the field and should tell the person what to correct. | Give each status a label that describes the record. Use **Draft**, **Open**, **Paused** and **Ended** for campaigns. Use **Under review**, **Approved** and **Not eligible** for qualifying actions, with a concrete reason for ineligibility. Use **Ready to use**, **Redeemed** and **Expired** for promo codes. Use **Scheduled**, **Processing**, **Paid** and **Failed** for payouts when the corresponding event is recorded. Pair a failed payout with the amount, the recorded reason if available and the appropriate recovery action. ## Interaction and accessibility - Keep the main action in a filled aubergine button. Use an outlined button for a consequential alternative and a text link for navigation. Use a stable label and show progress for operations that take time. - Keep controls comfortable to use on a phone. Target at least 44 × 44 CSS px for key mobile actions and preserve visible focus on every keyboard-operable control. Underline links in running text and pair icon-only controls with accessible names. - Use visible form labels and associate help and errors with their inputs. Preserve form values during recoverable failures. Announce status updates such as a copied offer link and return focus to the opener when a dialog closes. - Pair status, category and validation colors with words or meaningful symbols. Use a tested foreground and surface pairing for text and focus on both light and dark sections. Aim for at least 4.5:1 for normal text, 3:1 for large text and 3:1 for required visual features of controls and indicators. [WCAG 2.2](https://www.w3.org/TR/WCAG22/) - Keep motion brief and tied to feedback. Respect reduced-motion settings. Let layouts reflow with text enlargement. Put the qualifying action, amount and terms ahead of ornamental material on narrow screens. ## Photography Show the everyday work of Filipino creators and business owners. A creator might film an app walkthrough at a dining table. A store owner might arrange pastries or discuss a deal with a creator at the counter. A customer might look up the terms on a phone before ordering. - Use believable Philippine settings. Let the surroundings establish place through shopfronts, storefront materials, counters, natural interiors and available light. Cast a range of ages, skin tones, styles and occupations across the library. - Capture people in the middle of work with relaxed expressions and usable hand or phone poses. Favor ambient daylight, honest skin texture, warm neutral grading and recognizable surroundings. - Compose for a wide frame, a portrait crop and the offer-card crop. Keep faces and the action that explains the scene within the middle of the image. Place offer terms and any promo code in the interface where they stay sharp and accessible. - Write alternative text about the action or information the image contributes. Use empty alt text for imagery that serves only as decoration. Record whether each asset is generated or photographed, and use generated scenes as representative artwork. | Showcase asset | Scene | | --- | --- | | [`trim-creator.jpg`](assets/trim-creator.jpg) | A creator filming with a baker at a neighborhood bread counter. | | [`trim-fieldwork.jpg`](assets/trim-fieldwork.jpg) | Two creators reviewing a phone at a studio table. | | [`trim-counter.jpg`](assets/trim-counter.jpg) | A bakery owner setting out ensaymada. | All three photographs are generated editorial examples. The generation prompts are in the [photography notes](assets/PHOTO-NOTES.md). ## Token exports - [`tokens.json`](tokens.json) is the editable source for palette scales, semantic aliases, layout and component values. Update an alias when a role changes and a primitive when the whole system should inherit the change. - [`tokens.css`](tokens.css) is the browser export. Import it before component styles. For example, `color.surface.canvas` becomes `--color-surface-canvas`, and `font.family.heading` becomes `--font-family-heading`. Prefer semantic aliases and component tokens in product CSS. - [`fonts.css`](assets/fonts/fonts.css) loads the bundled variable fonts. Keep it with the neighboring font and license files when moving it to another application. - Run `node scripts/build-tokens.mjs` to regenerate the browser export and `node scripts/build-tokens.mjs --check` to verify that the export matches the source.