# Example campaign component notes

Fictional Northline campaign fixture from Derrick.dk, 11 October 2026.
This is a handover reference, not a Webflow library or import.

## Campaign request

Start with a project enquiry page. Create an event registration page using longer copy, one approved proof item and the existing visual system. Use the intended owner account. Ask for help where the current choices do not support the task, and record why.

## Exposed choices in the browser fixture

- Campaign headline: editable text, up to 180 characters as a demonstration input limit.
- Proof: three fictional names, one name or no proof section.
- Form: project enquiry or event registration.
- Section order: proof then form, or form then proof.
- Full or narrow layout preview: a viewing aid, not an actual device test.

## Fixed in the fixture

Type, colour, spacing and the two form structures. Both require name and email; the enquiry also requires a request. The test confirmation runs in the browser and sends nothing. The JSON download records content choices; it cannot be imported into Webflow.

## Decisions for a real library

Name exposed properties for their job. Agree supported proof counts and form variants. Record which site role edits content, which assembles pages, who reviews and who publishes. Identify the receiving system and how to inspect a test record. Keep shared structure and styles in the appropriate main component rather than making every detail editable.

## Done when

The future owner completes the task using the agreed account and notes. Keep the actual page, form destination evidence, tested device list, review outcome and remaining questions. Do not invent a completion time or a client outcome from this fictional example.