Feature phone, one text each way

A drawn keypad phone holding one question and one answer, beside a short explanation: no app and no script.

Product tourFreeFrom Isuka, Africa experienceAbout 6k tokens saved
The whole page

Links in the preview stay on the block.

Open on its own

The prompt

One prompt, written to stand on its own: goal, structure, type, colour, spacing, behaviour and the words in square brackets to replace. Paste it into any tool that writes HTML. The Code tab has this block as one file.

717 words
Download .zip
# Feature phone, one text each way

One product tour section, not a whole page: build it to drop into a page that already exists. Works in Claude, v0, Lovable, Bolt, Cursor or any tool that writes HTML.

## Goal
A section for a service that works over plain text messages: a drawn keypad phone shows one question and one answer beside a short explanation.

## Structure
1. Section on a pale panel, two columns
2. Left: an h2 in heavy condensed capitals
3. Left: one paragraph, a note above a hairline
4. Right: a drawn phone, screen well, round key cluster, twelve keys
5. Over the screen: a header with sender and time, on a rule
6. Thread, bottom aligned: outgoing bubble, sent stamp, incoming bubble

## Type
Big Shoulders Display 900 for the h2, uppercase, clamp(52px,6.2vw,104px)/.86. Wix Madefor Text 400 to 600 elsewhere: body 18px/1.5, 17px under 760px; paragraph measure 22em; note 500 15px/1.5, measure 26em. Keypad digits 500 15px. Screen type is in container units of the phone width, so it scales with the drawing: 4.3cqw/1.36, header 600 with its time at 500, stamp 500 at max(11px,3.4cqw).

## Colour
Ink #0D0D0D page, paper #F5F3F0 panel, screen #D9D5CE, body text #5C5751, key digits #A9A39C, selection #8E1B12. Shell ink with a #1C1B1A screen well, #22211F keys, a #33312E earpiece. The outgoing bubble is ink with #D9D5CE text; the incoming one keeps the screen colour with a 1.5px ink border, so the sides differ by shape, not colour. Ink and #5C5751 on paper, #D9D5CE on ink, pass AA.

## Spacing and lines
Section padding clamp(112px,15vw,220px) by clamp(20px,5vw,80px). Grid 1200px at most, columns 5fr and 6fr, gap clamp(56px,8vw,140px), centred. Paragraph 30px under the h2, note 44px under that, 20px above its text on a 1px rgba(13,13,13,.18) rule. Phone clamp(280px,25vw,340px) wide on a 320 by 680 box, radius 56px. The screen sits at 10.625% left, 10.882% top, 78.75% wide, 41.176% tall, padded 4cqw. Bubbles padded 2.4cqw by 3.2cqw, radius 3cqw with a 0.8cqw tail corner, 1.6cqw apart.

## Behaviour
No script is needed beyond entrances: the block has no states and the same two messages show at rest. The heading and both paragraphs rise 20px and fade in once when the section enters view, 0.7s cubic-bezier(.2,.7,.2,1), 60ms apart, from an IntersectionObserver at a 0.12 threshold that stops watching each element after it shows. Reduced motion: skip the entrance, paint the final state.

## Responsive
Under 760px one column with the copy above the phone, body 17px, phone min(300px,80vw). The screen needs no breakpoint: its type is in container units.

## Accessibility
The figure is labelled as a text conversation. The drawn phone is aria-hidden; header, messages and stamp are real text, so keep DOM order the same as screen order. Focus ring 2px currentColor, offset 4px.

## Built values (from code.html)
- Fonts: Big Shoulders Display 600, 800, 900 (Google Fonts); Wix Madefor Text 400, 500, 600 (Google Fonts).
- Colour variables: --ink #0D0D0D, --paper #F5F3F0, --ox #8E1B12, --mute #A9A39C, --mute-ink #5C5751, --lcd #D9D5CE.
- Font variables: --disp "Big Shoulders Display", "Arial Narrow", sans-serif; --text "Wix Madefor Text", ui-sans-serif, system-ui, sans-serif.
- Size variables: --pad clamp(112px, 15vw, 220px), --gut clamp(20px, 5vw, 80px), --col clamp(380px, 38vw, 600px).
- Media queries: max-width 760px.
- No media files.
- Script: yes, a small inline script.

## Content to replace
- [Headline]: four to six words on needing no app
- [Paragraph]: two sentences: who sends, what returns
- [Note]: one line naming the languages covered
- [Thread header]: the service name and a time
- [Outgoing message]: about ten words, as a person texts
- [Incoming reply]: two or three short sentences, one figure

## Rules
Plain, specific copy that reads as a live product; never the word sample. No shadows, glow, glass, blur, gradient text, emoji or italics. Motion moves transform and opacity, with colour, border, height and stroke transitions on state changes, and holds its end state under prefers-reduced-motion. Text passes WCAG AA.

## Output
Return the block in one piece: the markup, one style block with the web fonts imported on its first line, and a small script only if the behaviour needs one. No page wrapper, no framework, no build step. Prefix every class with `blk-` and put the colours and sizes in CSS variables at the top.

More like this

Product tour

Every product tour block