A practical manual for the two working applications, with clear instructions and real examples. Learn the controls, understand their limits and avoid publishing placeholder or fictional information.
Channel Mission Architect saves a working campaign plan. Campaign Landing Studio produces the public destination the buyer actually sees. Both save their own editable JSON projects independently. Neither automatically talks to Ghost Control or a web server.
Channel Mission Architect begins by asking who you want to reach, what you can offer and which channel you can access. The name is for your own working files; it does not appear in your customer-facing marketing unless you publish the separate campaign report.
Example: Write “Approach five relevant local accountants with a payroll preparation resource” rather than “become viral”.
The route dropdown offers eight distinct channel patterns. Each produces different task suggestions: partner conversations are not a social-post calendar, and search-ready content is not cold outreach. Change the channel when the route no longer fits.
Example: A one-person service with three free hours may choose warm introductions; a creator with a content archive may improve a useful public resource.
The duration sets suggested days for preparation, activity and review. All tasks are editable after generation. Hours per week and spend describe your real constraints, not fictional ROI calculations.
Example: For a two-week partner experiment: prepare on days 1–3, make a few respectful contacts on days 5–10, then record answers and next actions.
Every generated task has editable wording, a detailed notes area, owner, planned day and completion checkbox. Change the wording to name a real person, place, publication or asset. Add or remove tasks freely.
Example: Replace “Contact partners” with “Ask the manager of Smith & Co. whether a payroll checklist would help new employers”.
Open Field Notes to record the placement, hypothesis, known attempts, replies, qualified enquiries, sales and what you learned. Unknown counts stay empty. A verified zero is different from not having access to the number.
Example: If you asked three partners and received one reply, enter three attempts and one reply. Do not estimate downstream page views without evidence.
Save JSON holds every editable task and your notes. Download campaign HTML produces a standalone printable report. Task CSV is useful for a spreadsheet or calendar. Open full preview shows that real HTML report in a separate window.
Example: Save the JSON before switching devices; it does not automatically synchronise with the Ghost Control dashboard.
Campaign Landing Studio is a separate application. Its public page should match the message used to reach the buyer and offer one believable next step. The presence of a button does not mean a form or remote lead collector is connected.
Example: If you advertise a first-payroll checklist, the page should start with that exact question—not a vague “Welcome to our company” introduction.
Editorial Split suits a story plus visual. Bold Stack foregrounds one message. Feature Mosaic works when the benefits carry the argument. Event Invitation emphasises the invitation. Minimal Letter offers a more personal editorial style. Layouts change structure, not just colours.
Example: Try the same bookkeeping offer in Bold Stack and Minimal Letter. Choose whichever helps your real audience understand the offer faster.
Ten coordinated colour recipes are available, followed by editable background, text, accent and supporting colour controls. Use appropriate contrast. The Ghost member theme is deliberately independent: your clients should never inherit Ghost branding.
Example: A local florist might prefer a soft botanical palette; a technology studio might prefer clear dark blue. Neither needs a tactical intelligence aesthetic.
The builder exposes the headline, small category label, explanation, buttons, feature section heading and feature cards, proof heading/source, FAQ questions and answers, footer wording and link label. Leave optional fields empty: unused blocks are omitted from the exported HTML.
Example: No customer review to share? Leave that section blank and it will disappear from your public page. You can do the same with optional questions.
The embedded preview uses the exact markup intended for export. Switch among desktop, tablet and phone widths. Use Open full preview for a browser-window look at the real page. Verify both design and links after exporting.
Example: On a phone, check that your heading wraps well and that the main action can be tapped without searching around the page.
Download public HTML plus the project JSON. Test the HTML independently before deploying it to your own hosting. The generated output has no Ghost membership gate. Add a real public URL to your Territory record once published; Ghost does not upload, index or measure it automatically.
Example: If you use a separate booking provider or newsletter service, connect its genuine public URL. This static builder cannot create a backend from a field.
Imagine a fictional small service business preparing a first-payroll resource. In Channel Mission Architect, name the buyer and choose a partner route. Generate a short plan, then replace any broad tasks with specific local partners and realistic dates. Export the project JSON. In Campaign Landing Studio, choose an appropriate composition, describe the resource in ordinary language and add a working next-step URL. Choose an independent colour recipe and check the full preview. Leave proof blank unless you have authentic evidence; export the HTML and JSON separately. Publish only when the public page has been checked and you have a legitimate placement. Finally, record any real replies or observations in the field plan and Ghost Observatory.