The case for it

You could build all of this yourself

Making a page that rearranges itself around its readers takes several separate jobs. You could write every one of them yourself, and it would work.

The work

Who writes each part

What each job takes on your own, and what comes with Loom

	On your own	With Loom
Somewhere to keep the shape of the pageso that moving a section is not a code change	You build it	✓
Counting what readers dowhich parts they reach, how long they stay, what they press	You wire it up	✓
Asking a model for a changethe request, and a shape for the answer that comes back	You write it	✓
Checking a change against your own rulesbefore anybody reading the page sees it	You write it	✓
Putting a change backwithout working out by hand what it replaced	You write it	✓
Your componentsthe React you have already written	Yours	Yours
Which AI model it usesLoom is AI model agnostic	Yours	Yours

What stays yours

You still write your components and choose your model

Your components

Loom does not write code into your components and it does not replace them. You say which ones it is allowed to use.

Your model

Loom is AI model agnostic. Point it at the model you already use, or at one of your own.

Your rules

You write what an AI model is allowed to change on your page. Anything outside that is rejected, and Loom tells you why.

What comes with it

The rest of it is already written

Your page is kept as data rather than as code, so changing it is a write rather than a deploy. Your components do not change at all.

Your page reports what readers do with it, in a form your model can read. You do not have to pick an analytics product and then translate its charts into something a model can act on.

Every change is checked against your rules before anybody reading the page sees it, and it is stored with the way back. Putting one back is a single press.

What you build with

Every one of these comes with it

All 107 come with the install. Some are a whole section of a page and some are one piece inside it.

ActionArticleArticle gridAvatarAvatar rowBackdropBadgeBannerBefore afterBookBook gridBrandButtonCalloutCardCarouselCodeCode spanComparisonComparison rowComparison tableCredentialCredential gridDialogDividerEmbedEmphasisEmpty stateEventEvent gridFAQFAQ listFeatureFeature gridFeedFieldFooterFormFrameGridHaloHeadingHeroIconInline linkKbdLightboxLinkLink listLink pagerLink trailListList itemListingListing gridLogoLogo cloudMarqueeMediaMenuMessageMessage listMeterMilestoneMilestone listMilestone rowMosaicNavOfferingOffering gridOptionOrbitOverlayPagePerkPerk listPerk list itemPersonPerson gridPinPlatePopoverProductProduct gridProseQuoteQuote gridRatingRecordingRecording gridRevealSectionSpecSplitStackStatStat chartStat gridTableTable cellTable rowTallyTierTier tableTrendVoicesWaiting state

On a page

What they look like together

Every piece of this is a part from the list above.

Fresh coffee every Friday

Posted the morning it is ground.

Choose your roast

Light, medium or dark.

Pause any week

No phone call.

No contract

Stop whenever you like.

1Hero

2Feature grid

Who is reading it

The same page arranged for someone else

The page on the left is the one above. On the right is what a visitor who came looking for a gift gets.

As you built it

Fresh coffee every Friday

Posted the morning it is ground.

Choose your roast

Light, medium or dark.

Pause any week

No phone call.

No contract

Stop whenever you like.

For a visitor buying a gift

Send fresh coffee every Friday

Posted the morning it is ground.

Send it as a gift

With a note you write.

Choose your roast

Light, medium or dark.

Pause any week

No phone call.

Try it on a page of your own

This site is a Loom application too, built out of the same set. Putting it in a project you already have is what the docs are for.

Read the docs