Next workshop If you need the tech to explain it, you don't have a product RSVP now

ghostMarketingFlow

A content and email marketing playbook for Ghost: methodology plus an executable plugin.

Read the code: github.com/vibe2value/ghost-marketing-flow

Start from the template: ghostMarketingFlow was cloned from the vibe2value base at github.com/vibe2value/vibe2value. Clone it to start your own.

A content and email marketing playbook for Ghost: methodology plus an executable plugin.

The intent: take a small audience and move them across awareness, consideration and decision using Ghost's content and email surface. For the day-two operator who needs reads to convert into conversations, not just impressions into likes.

Built in public. The site you are on is part of the live demonstration.

What ghostMarketingFlow is

A content and email marketing playbook for Ghost: a methodology the operator runs themselves, plus a flowRun plugin that executes it. It moves a small audience across awareness, consideration and decision so reads turn into workshop signups and 1:1 conversations, with concrete signals at each stage. The first flowRun plugin, and the live demonstration is this site.

The 27 ideas

ghostMarketingFlow is built one idea at a time across the framework. Each idea has its own post and produces one file in the repo. The post works through the idea; the file is ghostMarketingFlow's worked result. The whole set reads in about ten minutes.

IdeaWorked example
1.1.1 - If You Can't Name the User, You're Guessing What They Wantshape/user.md
1.1.2 - Describe the Pain Without Mentioning the Solutionshape/problem.md
1.1.3 - The One-Line Promise That Keeps Your Build Honest Throughoutshape/promise.md
1.2.1 - Can You Explain This in 30 Seconds Without Mentioning the Tech?shape/positioning.md
1.2.2 - What Does "Success" Actually Mean for the First Version You Ship?shape/success.md
1.2.3 - The Risks You're Avoiding Naming Are the Ones That Bite Youshape/risks.md
1.3.1 - The One Outcome That Makes This Build Worth Doing in the First Placeshape/goal.md
1.3.2 - What This Will Not Do (On Purpose) Is Half the Decisionshape/scope.md
1.3.3 - Describe One Main Path First, Then Ignore Everything Elseshape/path.md
2.1.1 - The Only Path Your Prototype Actually Needs to Walkbuild/prototype-path.md
2.1.2 - Where the User First Feels Value Is Where to Start Buildingbuild/first-value-moment.md
2.1.3 - What This Build Is Meant to Teach You, Not Just to Shipbuild/learning-goal.md
2.2.1 - The Routine Work Checklist Nobody Talks Aboutbuild/routine-checklist.md
2.2.2 - Buy vs Build Is a Strategy Choice, Not an Engineering Onebuild/buy-vs-build.md
2.2.3 - Understanding the Shape of the System Before You Change Itbuild/system-shape.md
2.3.1 - Where the Real Differentiation Actually Lives in Your Buildbuild/differentiation.md
2.3.2 - Why Cutting Features Is a Design Skill Most Builders Skipbuild/feature-cut.md
2.3.3 - The One Metric That Proves This Works for Real Usersbuild/proof-metric.md
3.1.1 - Why Sharing Early Creates the Learning Your Build Needslaunch/early-sharing-plan.md
3.1.2 - Ask for Signals, Not Opinions, From the People You Trustlaunch/decision-signal.md
3.1.3 - Decide in Advance What Would Change Your Mindlaunch/decision-threshold.md
3.2.1 - The Difference Between Learning and Being Stucklaunch/learning-signal.md
3.2.2 - Explain Your Decisions Before Asking for Reviewlaunch/review-context.md
3.2.3 - Iteration Should Increase Value, Not Just Add Surface Arealaunch/iteration-value-test.md
3.3.1 - What "Ready" Actually Means Once Real Users Are Lookinglaunch/readiness-rule.md
3.3.2 - Name the Risks Yourself Before Users Find Them in Productionlaunch/launch-risks.md
3.3.3 - Are You Comfortable Putting Your Name on This Build?launch/ownership-check.md

Key takeaway

The posts teach the framework. This page is the short version of ghostMarketingFlow. The repo holds the worked files, one per idea, building up as the build does. Read the post for the thinking, open the file for the decision.