Make the page worth reading.

Start here

1. Choose your scope. In the workspace, select an Organization and Website. You only see scopes your account can access.
2. Set direction. In Branding choose colors and layout; in Context add the audience, purpose and reviewed source material.
3. Build a page. Pages lets you select ordered sections, write in the rendered preview, save drafts and review the saved result.
4. Hand it off. Export a marked prototype or reviewed HTML/Astro package for a developer. Review links, forms, SEO and permissions before anything goes live.

Some controls depend on your role or environment. If a button is disabled, read its nearby explanation; it does not mean Copyline saved or sent anything in the background.

Find your way

Branding → Context → Pages is the everyday path. The Organization and Website selectors sit above these tabs. Manage and Account are in your profile menu; this guide and the Support email are also linked there and at the bottom of the workspace.

On desktop, Pages has an outline, rendered-page preview and Writing and review tools. You can hide or restore either side pane and resize the columns. Those layout preferences are stored in this browser, not in the saved page. On narrow screens the same controls stack vertically. Inline undo and redo apply to the current unsaved editing session only.

Success and error notices appear as Copyline messages, not browser alerts. A styled confirmation asks before in-app navigation discards unsaved work; Keep editing or Escape leaves it intact. A browser-controlled tab-close/reload warning may still appear because the browser does not allow websites to restyle it.

Branding: set the visual direction

Set a website’s primary, accent, background and text colors, typography, button shape and page layout, then choose Save design choices. The preview uses these saved choices; changing a color field without saving does not create a revision or update the website for teammates.

You can ask Copyline to suggest a palette from a public URL or a supported screenshot, then review its contrast and save deliberately. Sampling is bounded: a URL may be inaccessible or unsuitable and Copyline will explain the failure rather than silently save colors. Private brand assets, when configured, belong to their selected website. A preview is not proof that an exported site has been deployed.

Context: audience, purpose and evidence

Describe who the website serves, what it should help them do, and which outcomes the team tracks. Save audience direction separately from page copy. Team measures are planning information; they are not automatically sent to the AI writer as evidence.

The one website-level source library lives here. Paste text, upload an allowed text file or preview a bounded public-page capture; inspect what was collected before saving. A pasted existing-page URL in page setup is only a reference and does not crawl that page. Newly added sources are unapproved. A reviewer or manager must approve suitable source material before it can be used as reviewed writing context. In Pages, you may choose reviewed sources for a particular section; selection does not turn an unapproved claim into fact. Do not upload credentials, private customer analytics or material you are not authorized to share.

Pages: create a structured draft

Select Add a page to set a slug, title, optional existing-page URL, SEO description, page purpose, competitor observations and writing guidance. The URL can suggest a slug, but Copyline currently stores a single path segment; it does not preserve an entire nested original path or import the old page. Competitor notes and writing guidance are internal page context, not approved citations.

Choose and reorder the sections you need. The default starting set is Hero, Trust and evidence, Offer, FAQ and Call to action. Other available types include narrative, comparison, decision strip, resource/lead magnet and general sections. Create draft page saves the page, selected sections and their first revisions together. Bracketed example text is a starting scaffold: replace it with reviewed, accurate copy before submitting for review. You can later add another section to a draft page and use its outline to choose a section.

Use Page details and focus to revise the saved title, search description, page audience, intended next step, primary reader question and page context. Save that form explicitly. Website Context describes the whole site; page focus explains this specific page.

Write on the rendered page

Choose Edit text on page to change supported headings and paragraphs where they appear in the preview. Save changes creates a new draft revision and refreshes the saved page. Discard edits removes only the unsaved visual edits, after confirmation. Done editing is unavailable while visual edits remain unsaved. A mobile-width preview changes your view; it does not change the saved design.

For links, lists, section type and other structure the visual editor cannot safely change, open Advanced: edit section source. This is Markdown with section-type metadata. Choose Save draft to create a revision; changing text in the field alone is not a save. The page preview and review checks operate on saved content. Copyline guards against overwriting a newer revision: if a colleague saved first, reopen the latest page and reconcile your changes instead of forcing a stale draft over theirs.

Revisions, history and activity

Each section save creates a numbered, dated revision. Open Revision history to inspect past saved versions; a permitted editor can restore an older one as a new draft revision, preserving the historical record instead of rewriting it. Page details, source actions and page status have their own saved and audited changes. People and activity separates live viewers from attributed changes, status history and AI proposals; an AI suggestion is not attributed as a human-approved revision until someone explicitly applies it.

Undo/redo in the visual editor only changes unsaved text in the current session. It does not undo a server-side revision or replace revision history. Before switching websites or leaving a dirty form, choose whether to save or leave those edits behind. Signing back in after an expired session does not recover text that was never saved.

Review and editorial status

Run review checks the saved page, not unsaved form fields or live website pages. Its eight rule-based areas are copy patterns, goal and audience, resource placement, voice, word count, sentence length, on-page title/headings and internal links. Findings are prompts for human judgement; they are not factual verification, a live link crawler or a quality score. Save changes, then rerun review to see updated findings.

A section can move from Draft to Ready for review, then be Approved by a reviewer or manager. Review and approval are distinct from marking the overall page Ready or Complete. Page status is versioned and appears in activity; Complete describes editorial progress, not publication. A completed page must be reopened as a draft before further copy edits. Bracketed example text blocks review readiness. Always verify claims, assets, links, legal language and accessibility yourself before handoff.

AI writer, when enabled

The AI writer works on one selected saved section at a time. Write a specific message, optionally select approved section sources, and send only after your page changes are saved. A completed response is a proposed edit shown on the page and in its own history: it is not saved copy. You can edit the proposed Markdown and preview it. Choose Apply as draft to save a new revision; stale suggestions from an older saved revision are read-only. A follow-up links to an earlier section suggestion for that same saved revision, not to every section on the page. Multi-section page-wide AI rewriting is not available.

Availability depends on your organization, website, role, environment and approved cost/data policy. Each message can be a separate provider request and charge. Local AI and Production AI are currently off; the hosted Staging exception is limited to a synthetic internal test site. An application ledger allowance does not establish a provider-wide spending cap. Never submit customer copy to a test writer or treat a generated assertion as verified evidence.

Export and developer handoff

Under Export options, Copy text copies the saved page text, not an unsaved edit. A reviewer or manager can choose Export HTML for a single page, Export Astro for a one-page ZIP, or Download site ZIP for the full-site Astro package. Exports are audited handoffs, not hosting or domain publication. A page with draft sections may be exported as a visibly draft prototype; draft HTML is marked noindex. Review every exported file before using it. The Astro starter includes editable site data, original section Markdown and handoff guidance; its preview/default build is noindex. The single-page ZIP may need cross-page links connected during integration.

Copyline does not automatically configure a customer domain, connect a CRM, deliver a PDF, activate a form, push to GitHub or publish a visitor-facing site. Exported designs and calls to action can be illustrative or intentionally inert. A developer must implement and test real links, forms, legal/consent behavior, SEO indexing and delivery before a separate approved launch. Never mistake downloading a ZIP or marking a page Complete for launching it.

People, roles and sign-in

Use Manage for organizations, websites, groups and memberships when your role allows it. Organization administrators manage organization access; group administrators work within their group. Website viewers are read-only, editors can draft, and reviewers/managers can approve or export according to their granted scope. Platform administration alone does not grant another customer’s editorial content; approved, time-limited support entry is audited. Do not share a sign-in or assume an email address alone creates membership in another tenant.

Under Account, sign-in and password guidance reflects the active provider. WorkOS-hosted sign-in may require an authenticator challenge; recovery must follow the configured provider and your workspace administrator. The Better Auth sign-in is retained only as an explicitly managed rollback path, not as a second ordinary login button. If your session ends, sign in again; saved revisions remain, unsaved fields may not. Sign out when you finish on a shared device.

When something does not look right

• An action is disabled: confirm your organization, website, role, page state and whether the section has unsaved edits. AI and invitations can also be disabled by environment.
• A change is missing: compare the selected page and saved revision, reopen Revision history, and check for a three-second status/error message. Do not repeatedly save over a colleague’s newer revision.
• A public URL or palette fails: check that it is public and eligible for bounded sampling. Do not send cookies, request headers or private material to Support; share the URL and the visible error only if appropriate.
• You suspect missing customer data: stop editing that site and contact Support. A release rollback does not restore overwritten customer content. Recovery requires a separately approved, verified backup and restore procedure; Copyline does not currently promise a customer recovery time or point.

Need help? Email patrick@dirigoinsights.com. Do not email passwords, MFA codes, session cookies, database URLs or private copy. Include the workspace version, the page or feature name, what you expected, and a non-sensitive description of what happened.