diff --git a/marketing/posts/post-01-docs-drift.md b/marketing/posts/post-01-docs-drift.md
new file mode 100644
index 0000000..5037790
--- /dev/null
+++ b/marketing/posts/post-01-docs-drift.md
@@ -0,0 +1,43 @@
+# Post Draft 01 — Docs Drift
+
+**Channel:** X + LinkedIn  
+**Theme:** Problem framing  
+**Goal:** Awareness + clickthrough to docs
+
+## Final copy (X)
+Your docs were correct when you wrote them.
+They break quietly when APIs change.
+
+That’s docs drift.
+
+Hype executes + validates Markdown code samples during generation, so stale examples fail in CI before users hit them.
+
+If docs are part of your product, they should be testable.
+
+Start: https://hypemd.dev?utm_source=x&utm_medium=social&utm_campaign=q2_launch
+Repo: https://github.com/gopherguides/hype
+
+## Final copy (LinkedIn)
+Most documentation failures are silent until users find them.
+
+Hype helps teams catch docs drift earlier by executing and validating code examples directly from Markdown during doc generation.
+
+That means stale snippets fail in CI instead of failing in front of customers.
+
+If documentation is product surface area, test it like product code.
+
+Start: https://hypemd.dev?utm_source=linkedin&utm_medium=social&utm_campaign=q2_launch
+Repo: https://github.com/gopherguides/hype
+
+## First comment/reply template
+If you want to test this quickly, run `hype export` in CI on one docs folder and fail on broken examples.
+
+## Media notes
+- Asset file: `marketing/assets/post-01-docs-drift.png`
+- Suggested asset: side-by-side screenshot (stale docs output vs CI failure from executable docs check).
+- Alt text: “Comparison of a stale code example in static docs versus a failing CI check using executable Markdown validation.”
+
+## Publishing metadata
+- Scheduled slot (CT): 2026-03-23 09:00
+- Owner: Hype maintainer
+- Status: copy ready, awaiting image export
diff --git a/marketing/posts/post-02-include-reuse.md b/marketing/posts/post-02-include-reuse.md
new file mode 100644
index 0000000..7ec7925
--- /dev/null
+++ b/marketing/posts/post-02-include-reuse.md
@@ -0,0 +1,39 @@
+# Post Draft 02 — Include Reuse
+
+**Channel:** X + LinkedIn  
+**Theme:** Workflow/value demonstration  
+**Goal:** Drive technical trial behavior
+
+## Final copy (X)
+Copy/pasting setup blocks across README, docs, and blog posts is maintenance debt.
+
+With Hype, write shared content once and reuse it with `<include>`.
+Update one source, propagate everywhere.
+
+Less drift. Faster updates. Cleaner docs architecture.
+
+Docs: https://hypemd.dev/docs?utm_source=x&utm_medium=social&utm_campaign=q2_launch
+Repo: https://github.com/gopherguides/hype
+
+## Final copy (LinkedIn)
+A common docs scaling issue: the same snippet exists in 4+ places, then drifts.
+
+Hype’s `<include>` pattern lets teams maintain one canonical source and reuse it across README, docs pages, and tutorials.
+
+When the source changes, every downstream page stays aligned.
+
+Docs: https://hypemd.dev/docs?utm_source=linkedin&utm_medium=social&utm_campaign=q2_launch
+Repo: https://github.com/gopherguides/hype
+
+## First comment/reply template
+Audit your top 10 duplicated snippets and convert one to a shared include this week.
+
+## Media notes
+- Asset file: `marketing/assets/post-02-include-reuse.png`
+- Suggested asset: mini diagram (one source snippet -> README + docs + tutorial outputs).
+- Alt text: “Diagram showing one canonical snippet reused across multiple documentation pages using include references.”
+
+## Publishing metadata
+- Scheduled slot (CT): 2026-03-25 11:30
+- Owner: Hype maintainer
+- Status: copy ready, awaiting image export