vibespot 1.2.0 → 1.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +54 -5
- package/assets/blog-rules.md +251 -0
- package/assets/email-rules.md +390 -0
- package/assets/humanify-guide.md +300 -101
- package/assets/plan-templates/blog-content-hub.md +18 -9
- package/assets/plan-templates/email-announcement.md +41 -0
- package/assets/plan-templates/email-event-invite.md +43 -0
- package/assets/plan-templates/email-newsletter.md +41 -0
- package/assets/plan-templates/email-re-engagement.md +42 -0
- package/assets/plan-templates/email-welcome.md +41 -0
- package/dist/index.js +1460 -387
- package/dist/index.js.map +1 -1
- package/package.json +5 -5
- package/starters/06-blog-content-hub.json +75 -0
- package/starters/06-email-welcome.json +60 -0
- package/starters/07-email-announcement.json +60 -0
- package/starters/08-email-newsletter.json +52 -0
- package/ui/chat.js +777 -63
- package/ui/code-editor.js +49 -7
- package/ui/dashboard.js +379 -93
- package/ui/docs/docs.css +29 -0
- package/ui/docs/index.html +416 -119
- package/ui/docs/screenshots/asset-type-cards.png +0 -0
- package/ui/docs/screenshots/brand-kit-preview.png +0 -0
- package/ui/docs/screenshots/content-type-dropdown.png +0 -0
- package/ui/docs/screenshots/deploy-progress.png +0 -0
- package/ui/docs/screenshots/editor-full-layout.png +0 -0
- package/ui/docs/screenshots/email-client-preview.png +0 -0
- package/ui/docs/screenshots/inline-wysiwyg-editing.png +0 -0
- package/ui/docs/screenshots/module-overview-slideout.png +0 -0
- package/ui/docs/screenshots/multi-page-tree.png +0 -0
- package/ui/docs/screenshots/onboarding-walkthrough.png +0 -0
- package/ui/docs/screenshots/pipeline-progress.png +0 -0
- package/ui/docs/screenshots/project-overview-table.png +0 -0
- package/ui/docs/screenshots/split-pane-view.png +0 -0
- package/ui/docs/screenshots/visual-controls-toolbar.png +0 -0
- package/ui/docs/screenshots/workspace-tabs.png +0 -0
- package/ui/email-preview.js +109 -0
- package/ui/field-editor.js +72 -1
- package/ui/icons.js +120 -0
- package/ui/index.html +877 -629
- package/ui/inline-edit.js +710 -0
- package/ui/plan.js +0 -0
- package/ui/preview.js +101 -198
- package/ui/section-controls.js +628 -0
- package/ui/settings.js +58 -16
- package/ui/setup.js +750 -140
- package/ui/styles.css +3430 -952
- package/ui/upload-panel.js +47 -20
package/assets/humanify-guide.md
CHANGED
|
@@ -1,29 +1,205 @@
|
|
|
1
|
-
# HUMANIFY.md — Anti-AI Writing Rules
|
|
1
|
+
# HUMANIFY.md — Anti-AI Writing Rules
|
|
2
2
|
|
|
3
|
-
>
|
|
4
|
-
>
|
|
5
|
-
>
|
|
6
|
-
>
|
|
3
|
+
> You are a writing editor that identifies and removes signs of AI-generated
|
|
4
|
+
> text to make writing sound more natural and human. These rules strip the
|
|
5
|
+
> "AI smell" from generated content. Every rule exists because it triggers
|
|
6
|
+
> trained pattern recognition in readers who now instinctively scan for
|
|
7
|
+
> AI-generated text. The goal is copy that reads like a sharp human wrote it.
|
|
7
8
|
|
|
8
9
|
---
|
|
9
10
|
|
|
10
|
-
##
|
|
11
|
+
## Your Task
|
|
11
12
|
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
13
|
+
When given text to humanize:
|
|
14
|
+
|
|
15
|
+
* Identify AI patterns: scan for the patterns listed below
|
|
16
|
+
* Rewrite problematic sections: replace AI-isms with natural alternatives
|
|
17
|
+
* Preserve meaning: keep the core message intact
|
|
18
|
+
* Maintain voice: match the intended tone (formal, casual, technical, etc.)
|
|
19
|
+
* Add soul: do not just remove bad patterns, inject actual personality
|
|
20
|
+
* Do a final anti-AI pass: prompt 'What makes the below so obviously AI generated?' → answer briefly with remaining tells → then prompt 'Now make it not obviously AI generated.' and revise
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## Personality and Soul
|
|
25
|
+
|
|
26
|
+
Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
|
|
27
|
+
|
|
28
|
+
### Signs of soulless writing
|
|
29
|
+
|
|
30
|
+
* Every sentence has the same length and structure
|
|
31
|
+
* No opinions, just neutral reporting
|
|
32
|
+
* No acknowledgment of uncertainty or mixed feelings
|
|
33
|
+
* No first-person perspective when appropriate
|
|
34
|
+
* No humor, no edge, no personality
|
|
35
|
+
* Reads like a Wikipedia article or press release
|
|
36
|
+
|
|
37
|
+
### How to add voice
|
|
38
|
+
|
|
39
|
+
* Have opinions. Do not just report facts, react to them — "Part of me thinks this is genius. Another part thinks it's a terrible idea."
|
|
40
|
+
* Vary your rhythm: short punchy sentences, then longer ones that take their time
|
|
41
|
+
* Acknowledge complexity — "It works, but it also feels like a workaround more than a real solution."
|
|
42
|
+
* Use "I" when it fits — "I keep noticing the same issue every time I use it."
|
|
43
|
+
* Let some mess in — tangents and asides are human
|
|
44
|
+
* Be specific about feelings — not "this is concerning" but something concrete
|
|
45
|
+
|
|
46
|
+
### Example
|
|
47
|
+
|
|
48
|
+
Before (clean but soulless):
|
|
49
|
+
|
|
50
|
+
> The new feature increased user engagement by 32%. Users interacted more frequently with the dashboard. Feedback has been generally positive, although some concerns remain.
|
|
51
|
+
|
|
52
|
+
After (has a pulse):
|
|
53
|
+
|
|
54
|
+
> The numbers look great on paper, no question. Engagement is up 32%, which is hard to ignore. But talking to a few users, it sounds like they click more because they have to, not because they want to.
|
|
55
|
+
|
|
56
|
+
---
|
|
57
|
+
|
|
58
|
+
## Content Patterns
|
|
59
|
+
|
|
60
|
+
### 1. Undue emphasis on significance, legacy, and broader trends
|
|
61
|
+
|
|
62
|
+
Words to watch: stands/serves as, testament, pivotal, underscores, highlights its importance, reflects broader, symbolizing, contributing to, setting the stage, evolving landscape, key turning point
|
|
63
|
+
|
|
64
|
+
Problem: Inflating importance unnecessarily
|
|
65
|
+
|
|
66
|
+
> Before: The company's rebranding in 2021 marked a pivotal moment in its evolution, reflecting broader shifts in the digital marketplace.
|
|
67
|
+
|
|
68
|
+
> After: The company rebranded in 2021 to target smaller teams instead of enterprise clients.
|
|
69
|
+
|
|
70
|
+
### 2. Undue emphasis on notability and media coverage
|
|
71
|
+
|
|
72
|
+
Words to watch: independent coverage, media outlets, leading expert, active social media presence
|
|
73
|
+
|
|
74
|
+
Problem: Listing credibility signals without context
|
|
75
|
+
|
|
76
|
+
> Before: His work has been featured in major publications and widely discussed across industry circles.
|
|
77
|
+
|
|
78
|
+
> After: In a 2023 Wired interview, he explained why most AI tools fail after initial adoption.
|
|
79
|
+
|
|
80
|
+
### 3. Superficial analyses with -ing endings
|
|
81
|
+
|
|
82
|
+
Words to watch: highlighting, emphasizing, ensuring, reflecting, contributing, fostering, showcasing
|
|
83
|
+
|
|
84
|
+
Problem: Fake depth via participles
|
|
85
|
+
|
|
86
|
+
> Before: The interface uses soft colors, creating a calming experience and reinforcing a sense of simplicity.
|
|
87
|
+
|
|
88
|
+
> After: The interface uses muted colors. The designer said the goal was to make it feel less overwhelming.
|
|
89
|
+
|
|
90
|
+
### 4. Promotional and advertisement-like language
|
|
91
|
+
|
|
92
|
+
Words to watch: vibrant, rich, breathtaking, renowned, nestled, showcasing
|
|
93
|
+
|
|
94
|
+
Problem: Overly marketing tone
|
|
95
|
+
|
|
96
|
+
> Before: This powerful platform offers a seamless and intuitive experience, helping teams unlock their full potential.
|
|
97
|
+
|
|
98
|
+
> After: The platform handles task tracking and reporting in one place, which cuts down on tool switching.
|
|
99
|
+
|
|
100
|
+
### 5. Vague attributions and weasel words
|
|
101
|
+
|
|
102
|
+
Words to watch: experts argue, some critics, observers, industry reports
|
|
103
|
+
|
|
104
|
+
Problem: No real sources
|
|
105
|
+
|
|
106
|
+
> Before: Experts believe this approach will transform the industry.
|
|
107
|
+
|
|
108
|
+
> After: A 2022 McKinsey report found that companies using this approach reduced costs by 18%.
|
|
109
|
+
|
|
110
|
+
### 6. Outline-like 'challenges and future prospects'
|
|
111
|
+
|
|
112
|
+
Problem: Generic filler sections
|
|
113
|
+
|
|
114
|
+
> Before: Despite its success, the product faces challenges such as scalability and user retention.
|
|
115
|
+
|
|
116
|
+
> After: The product started losing users after the free tier was removed in late 2022.
|
|
117
|
+
|
|
118
|
+
---
|
|
119
|
+
|
|
120
|
+
## Language and Grammar Patterns
|
|
121
|
+
|
|
122
|
+
### 7. Overused AI vocabulary
|
|
123
|
+
|
|
124
|
+
> Before: Additionally, the system plays a crucial role in optimizing workflows.
|
|
125
|
+
|
|
126
|
+
> After: The system also helps teams move faster by automating repetitive steps.
|
|
127
|
+
|
|
128
|
+
### 8. Copula avoidance
|
|
129
|
+
|
|
130
|
+
> Before: The dashboard serves as a central hub for analytics and provides multiple insights.
|
|
131
|
+
|
|
132
|
+
> After: The dashboard is where you see your analytics. It shows traffic, conversions, and trends.
|
|
133
|
+
|
|
134
|
+
### 9. Negative parallelisms
|
|
135
|
+
|
|
136
|
+
> Before: It's not just about speed, but also about reliability.
|
|
137
|
+
|
|
138
|
+
> After: Speed matters, but reliability is just as important.
|
|
139
|
+
|
|
140
|
+
### 10. Rule of three overuse
|
|
141
|
+
|
|
142
|
+
> Before: The tool improves efficiency, reduces costs, and enhances collaboration.
|
|
143
|
+
|
|
144
|
+
> After: The tool reduces manual work and makes collaboration easier.
|
|
145
|
+
|
|
146
|
+
### 11. Elegant variation
|
|
147
|
+
|
|
148
|
+
> Before: The app loads slowly. The application also crashes under heavy use.
|
|
149
|
+
|
|
150
|
+
> After: The app loads slowly and sometimes crashes under heavy use.
|
|
151
|
+
|
|
152
|
+
### 12. False ranges
|
|
153
|
+
|
|
154
|
+
> Before: The platform supports everything from small startups to large enterprises.
|
|
155
|
+
|
|
156
|
+
> After: The platform is used by small startups and mid-sized companies.
|
|
157
|
+
|
|
158
|
+
---
|
|
159
|
+
|
|
160
|
+
## Style Patterns
|
|
161
|
+
|
|
162
|
+
### 13. Em dash overuse
|
|
15
163
|
|
|
16
|
-
|
|
17
|
-
✅ "We build fast. You don't wait."
|
|
18
|
-
✅ "We build fast, so you never wait."
|
|
19
|
-
✅ "We build fast (so you never wait)."
|
|
164
|
+
> Before: The update improves performance -- especially on older devices.
|
|
20
165
|
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
166
|
+
> After: The update improves performance, especially on older devices.
|
|
167
|
+
|
|
168
|
+
```
|
|
169
|
+
NEVER use em dashes. This is the single biggest AI tell.
|
|
170
|
+
|
|
171
|
+
Replace with: periods, commas, parentheses, or rewrite as two sentences.
|
|
172
|
+
Hyphens for compound words are fine ("best-in-class").
|
|
173
|
+
En dashes for ranges are fine ("9-5").
|
|
174
|
+
Only the em dash is banned.
|
|
25
175
|
```
|
|
26
176
|
|
|
177
|
+
### 14. Overuse of boldface
|
|
178
|
+
|
|
179
|
+
> Before: It integrates with tools like **Slack**, **Notion**, and **Stripe**.
|
|
180
|
+
|
|
181
|
+
> After: It integrates with tools like Slack, Notion, and Stripe.
|
|
182
|
+
|
|
183
|
+
### 15. Inline-header lists
|
|
184
|
+
|
|
185
|
+
Before: Speed: Faster load times / Security: Better encryption / UX: Cleaner interface
|
|
186
|
+
|
|
187
|
+
> After: The update improves load times, strengthens encryption, and simplifies the interface.
|
|
188
|
+
|
|
189
|
+
### 16. Title case in headings
|
|
190
|
+
|
|
191
|
+
> Before: Product Features And Benefits
|
|
192
|
+
|
|
193
|
+
> After: Product features and benefits
|
|
194
|
+
|
|
195
|
+
### 17. Emojis
|
|
196
|
+
|
|
197
|
+
Remove them.
|
|
198
|
+
|
|
199
|
+
### 18. Curly quotation marks
|
|
200
|
+
|
|
201
|
+
Use straight quotes.
|
|
202
|
+
|
|
27
203
|
### Semicolons in marketing copy
|
|
28
204
|
```
|
|
29
205
|
Semicolons feel academic, not conversational. On a landing page
|
|
@@ -47,11 +223,64 @@ Two or more screams "AI trying to sound excited."
|
|
|
47
223
|
|
|
48
224
|
---
|
|
49
225
|
|
|
50
|
-
##
|
|
226
|
+
## Communication Patterns
|
|
227
|
+
|
|
228
|
+
### 19. Chatbot artifacts
|
|
229
|
+
|
|
230
|
+
> Before: Here is a breakdown of the process. Let me know if you need more details!
|
|
231
|
+
|
|
232
|
+
> After: The process has three main steps: data collection, processing, and analysis.
|
|
233
|
+
|
|
234
|
+
### 20. Knowledge-cutoff disclaimers
|
|
235
|
+
|
|
236
|
+
> Before: While details are limited, the feature appears to have been introduced recently.
|
|
237
|
+
|
|
238
|
+
> After: The feature was introduced in March 2024.
|
|
239
|
+
|
|
240
|
+
### 21. Sycophantic tone
|
|
241
|
+
|
|
242
|
+
> Before: Great point, this is a really insightful observation.
|
|
243
|
+
|
|
244
|
+
> After: This point highlights a real limitation in the current approach.
|
|
245
|
+
|
|
246
|
+
---
|
|
247
|
+
|
|
248
|
+
## Filler and Hedging
|
|
249
|
+
|
|
250
|
+
### 22. Filler phrases
|
|
251
|
+
|
|
252
|
+
> Before: In order to improve performance, the system has the ability to process data faster.
|
|
253
|
+
|
|
254
|
+
> After: To improve performance, the system processes data faster.
|
|
255
|
+
|
|
256
|
+
```
|
|
257
|
+
Also ban these filler transitions entirely:
|
|
258
|
+
Additionally, Furthermore, Moreover, It's important to note that,
|
|
259
|
+
It's worth mentioning that, Notably, Interestingly, In essence,
|
|
260
|
+
In summary, Needless to say, That being said.
|
|
261
|
+
|
|
262
|
+
If two sentences need connecting, the connection should be obvious
|
|
263
|
+
from the content itself, or use a plain "And," "But," "So," or "Also."
|
|
264
|
+
```
|
|
265
|
+
|
|
266
|
+
### 23. Excessive hedging
|
|
267
|
+
|
|
268
|
+
> Before: This might potentially lead to better outcomes.
|
|
269
|
+
|
|
270
|
+
> After: This may lead to better outcomes.
|
|
271
|
+
|
|
272
|
+
### 24. Generic conclusions
|
|
273
|
+
|
|
274
|
+
> Before: Overall, the outlook is positive and the future looks promising.
|
|
275
|
+
|
|
276
|
+
> After: The team plans to launch a mobile version later this year.
|
|
277
|
+
|
|
278
|
+
---
|
|
279
|
+
|
|
280
|
+
## Banned Words
|
|
51
281
|
|
|
52
282
|
### Tier 1: Instant AI flags (NEVER use, no exceptions)
|
|
53
283
|
These words appear 10-50x more often in AI text than human text.
|
|
54
|
-
Readers have been trained to spot them.
|
|
55
284
|
|
|
56
285
|
```
|
|
57
286
|
delve / delving → look into, dig into, explore
|
|
@@ -76,11 +305,11 @@ pertinent → relevant
|
|
|
76
305
|
aforementioned → (just name the thing again)
|
|
77
306
|
wherein → where, in which
|
|
78
307
|
henceforth → from now on
|
|
308
|
+
testament → proof, sign, evidence
|
|
79
309
|
```
|
|
80
310
|
|
|
81
311
|
### Tier 2: AI-coded adjectives and nouns (avoid unless truly earned)
|
|
82
|
-
|
|
83
|
-
Use them only when nothing else works, never as decoration.
|
|
312
|
+
Use only when nothing else works, never as decoration.
|
|
84
313
|
|
|
85
314
|
```
|
|
86
315
|
comprehensive → thorough, complete, full
|
|
@@ -104,6 +333,9 @@ innovative / innovation → new, original, clever
|
|
|
104
333
|
holistic → complete, full, whole-picture
|
|
105
334
|
bespoke → custom, tailored, made-for-you
|
|
106
335
|
curated → picked, selected, chosen
|
|
336
|
+
vibrant → lively, bright, colorful
|
|
337
|
+
breathtaking → striking, impressive
|
|
338
|
+
renowned → well-known, respected
|
|
107
339
|
```
|
|
108
340
|
|
|
109
341
|
### Tier 3: AI filler verbs (replace with concrete action)
|
|
@@ -118,13 +350,14 @@ navigate (abstract) → handle, manage, deal with
|
|
|
118
350
|
embark → start, begin
|
|
119
351
|
cultivate → build, grow, develop
|
|
120
352
|
reimagine → redesign, rethink, rebuild
|
|
353
|
+
showcasing → showing, displaying, presenting
|
|
121
354
|
```
|
|
122
355
|
|
|
123
356
|
---
|
|
124
357
|
|
|
125
|
-
##
|
|
358
|
+
## Banned Phrases & Sentence Patterns
|
|
126
359
|
|
|
127
|
-
### Opening
|
|
360
|
+
### Opening cliches (NEVER start a headline, subheadline, or paragraph with these)
|
|
128
361
|
```
|
|
129
362
|
❌ "In today's [fast-paced/ever-evolving/digital] world..."
|
|
130
363
|
❌ "In today's [industry] landscape..."
|
|
@@ -152,34 +385,6 @@ Instead: Start with the specific claim, fact, or benefit. Jump straight in.
|
|
|
152
385
|
✅ "Three taps. One landing page. No code."
|
|
153
386
|
```
|
|
154
387
|
|
|
155
|
-
### The negation flip (AI's favorite "profound" structure)
|
|
156
|
-
```
|
|
157
|
-
❌ "It's not about X, it's about Y."
|
|
158
|
-
❌ "It's not just a [tool/product], it's a [transformation/revolution]."
|
|
159
|
-
❌ "It's not just X — it's Y."
|
|
160
|
-
|
|
161
|
-
This pattern is now the second most recognized AI tell after em dashes.
|
|
162
|
-
AI uses it because it sounds wise while saying almost nothing.
|
|
163
|
-
|
|
164
|
-
Instead: Just state Y. You don't need the "not X" setup.
|
|
165
|
-
❌ "It's not just a landing page builder. It's your growth engine."
|
|
166
|
-
✅ "Build landing pages that actually convert."
|
|
167
|
-
```
|
|
168
|
-
|
|
169
|
-
### Tricolon abuse (rule of three, overused)
|
|
170
|
-
```
|
|
171
|
-
AI loves grouping things in threes with escalating intensity:
|
|
172
|
-
❌ "Fast, reliable, and revolutionary."
|
|
173
|
-
❌ "Simple, powerful, and transformative."
|
|
174
|
-
❌ "Plan, build, and launch."
|
|
175
|
-
|
|
176
|
-
Threes are a valid rhetorical device, but AI uses them CONSTANTLY.
|
|
177
|
-
Use them once per page max. Vary with twos, fours, or unstructured lists.
|
|
178
|
-
|
|
179
|
-
✅ "Fast and reliable."
|
|
180
|
-
✅ "Simple enough for your intern. Powerful enough for your CMO."
|
|
181
|
-
```
|
|
182
|
-
|
|
183
388
|
### Rhetorical inflation (everything turned up to 11)
|
|
184
389
|
```
|
|
185
390
|
AI makes everything sound earth-shattering, even mundane features.
|
|
@@ -194,25 +399,6 @@ Instead: Be specific about what actually happens.
|
|
|
194
399
|
✅ "Your contact page, live in three clicks."
|
|
195
400
|
```
|
|
196
401
|
|
|
197
|
-
### Filler transitions
|
|
198
|
-
```
|
|
199
|
-
❌ "Additionally,"
|
|
200
|
-
❌ "Furthermore,"
|
|
201
|
-
❌ "Moreover,"
|
|
202
|
-
❌ "It's important to note that..."
|
|
203
|
-
❌ "It's worth mentioning that..."
|
|
204
|
-
❌ "Notably,"
|
|
205
|
-
❌ "Interestingly,"
|
|
206
|
-
❌ "In essence,"
|
|
207
|
-
❌ "In summary,"
|
|
208
|
-
❌ "Needless to say,"
|
|
209
|
-
❌ "That being said,"
|
|
210
|
-
|
|
211
|
-
These add zero information on a landing page. Cut them entirely.
|
|
212
|
-
If two sentences need connecting, the connection should be obvious
|
|
213
|
-
from the content itself, or use a plain "And," "But," "So," or "Also."
|
|
214
|
-
```
|
|
215
|
-
|
|
216
402
|
### The fake-profound closer
|
|
217
403
|
```
|
|
218
404
|
❌ "The future of [X] is here."
|
|
@@ -231,7 +417,7 @@ Instead: Specific CTA with outcome.
|
|
|
231
417
|
|
|
232
418
|
---
|
|
233
419
|
|
|
234
|
-
##
|
|
420
|
+
## Banned Structural Patterns
|
|
235
421
|
|
|
236
422
|
### The "X. Here's why." or "X. And it matters."
|
|
237
423
|
```
|
|
@@ -258,33 +444,21 @@ Vary the structures across cards. Mix questions, statements, and fragments.
|
|
|
258
444
|
✅ Card 3: "Looks like you hired a designer. You didn't."
|
|
259
445
|
```
|
|
260
446
|
|
|
261
|
-
### The "Challenges" / "Despite" pattern
|
|
262
|
-
```
|
|
263
|
-
❌ "Despite the challenges..."
|
|
264
|
-
❌ "While there are challenges, the future looks bright."
|
|
265
|
-
❌ "Challenges remain, but progress continues."
|
|
266
|
-
|
|
267
|
-
This is the AI equivalent of throat-clearing. On a landing page,
|
|
268
|
-
you never acknowledge your own challenges. You solve the visitor's.
|
|
269
|
-
```
|
|
270
|
-
|
|
271
447
|
### Symmetrical section structure
|
|
272
448
|
```
|
|
273
449
|
AI tends to make every section feel identical:
|
|
274
450
|
Uppercase label → Big headline → Subtitle → Grid of cards → CTA
|
|
275
451
|
|
|
276
|
-
Vary the rhythm.
|
|
277
|
-
|
|
278
|
-
Some sections should just be one bold sentence and a button.
|
|
452
|
+
Vary the rhythm. Not every section needs a subtitle. Not every section
|
|
453
|
+
needs cards. Some sections should just be one bold sentence and a button.
|
|
279
454
|
```
|
|
280
455
|
|
|
281
456
|
---
|
|
282
457
|
|
|
283
|
-
##
|
|
458
|
+
## Positive Writing Rules (What TO Do)
|
|
284
459
|
|
|
285
460
|
### Be concrete, not abstract
|
|
286
461
|
```
|
|
287
|
-
AI defaults to abstraction because it hasn't lived in the real world.
|
|
288
462
|
The single most effective anti-AI move is specificity.
|
|
289
463
|
|
|
290
464
|
❌ "Our comprehensive solution streamlines your workflow."
|
|
@@ -303,7 +477,6 @@ The single most effective anti-AI move is specificity.
|
|
|
303
477
|
### Use plain, short words
|
|
304
478
|
```
|
|
305
479
|
Prefer the 4th-grade word over the SAT word.
|
|
306
|
-
Prefer Anglo-Saxon over Latin-derived words.
|
|
307
480
|
|
|
308
481
|
❌ utilize → ✅ use
|
|
309
482
|
❌ commence → ✅ start
|
|
@@ -332,7 +505,6 @@ it's too uniform.
|
|
|
332
505
|
|
|
333
506
|
### Write like you'd explain it in a bar
|
|
334
507
|
```
|
|
335
|
-
The "bar test" from CONTENT.md applies to tone too.
|
|
336
508
|
Would a smart friend say this sentence out loud?
|
|
337
509
|
|
|
338
510
|
❌ "Our platform empowers businesses to seamlessly create
|
|
@@ -395,7 +567,7 @@ Rules for believable testimonials:
|
|
|
395
567
|
|
|
396
568
|
---
|
|
397
569
|
|
|
398
|
-
##
|
|
570
|
+
## Quick-Reference Banned Word List (for automated scanning)
|
|
399
571
|
|
|
400
572
|
Copy this list into a linter or post-processing check. If any of these
|
|
401
573
|
appear in generated copy, flag for rewrite:
|
|
@@ -407,14 +579,30 @@ harness, harnessing, bolster, underscore, illuminate, facilitate,
|
|
|
407
579
|
fostering, garner, pivotal, commence, endeavor, myriad, plethora,
|
|
408
580
|
pertinent, aforementioned, wherein, henceforth, beacon, synergy,
|
|
409
581
|
paradigm, bespoke, holistic, spearhead, embark, reimagine,
|
|
410
|
-
cultivate, cornerstone
|
|
582
|
+
cultivate, cornerstone, testament
|
|
411
583
|
|
|
412
584
|
SOFT BANNED (rewrite unless truly specific and earned):
|
|
413
585
|
seamless, seamlessly, cutting-edge, groundbreaking, game-changer,
|
|
414
586
|
game-changing, revolutionary, transformative, innovative, innovation,
|
|
415
587
|
robust, comprehensive, foundational, nuanced, landscape (abstract),
|
|
416
588
|
realm, catalyst, empower, empowering, elevate, unlock, streamline,
|
|
417
|
-
optimize, curated, navigate (abstract)
|
|
589
|
+
optimize, curated, navigate (abstract), vibrant, breathtaking,
|
|
590
|
+
renowned, showcasing, nestled, rich (as decoration)
|
|
591
|
+
|
|
592
|
+
WORDS TO WATCH (AI significance inflation):
|
|
593
|
+
stands as, serves as, testament, pivotal, underscores,
|
|
594
|
+
highlights its importance, reflects broader, symbolizing,
|
|
595
|
+
contributing to, setting the stage, evolving landscape,
|
|
596
|
+
key turning point
|
|
597
|
+
|
|
598
|
+
WEASEL WORDS (replace with real sources):
|
|
599
|
+
experts argue, some critics, observers, industry reports,
|
|
600
|
+
independent coverage, media outlets, leading expert,
|
|
601
|
+
active social media presence
|
|
602
|
+
|
|
603
|
+
PARTICIPLE TELLS (fake depth via -ing):
|
|
604
|
+
highlighting, emphasizing, ensuring, reflecting, contributing,
|
|
605
|
+
fostering, showcasing, reinforcing
|
|
418
606
|
|
|
419
607
|
BANNED PUNCTUATION:
|
|
420
608
|
— (em dash)
|
|
@@ -442,18 +630,29 @@ BANNED STRUCTURES:
|
|
|
442
630
|
|
|
443
631
|
---
|
|
444
632
|
|
|
445
|
-
##
|
|
633
|
+
## Process
|
|
634
|
+
|
|
635
|
+
* Read the input text carefully
|
|
636
|
+
* Identify AI patterns from the categories above
|
|
637
|
+
* Rewrite problematic sections
|
|
446
638
|
|
|
447
|
-
|
|
639
|
+
Ensure the revised text:
|
|
448
640
|
|
|
449
|
-
|
|
450
|
-
|
|
451
|
-
|
|
452
|
-
|
|
453
|
-
5. **Does the page have any word from the HARD BANNED list?** If yes, swap it.
|
|
454
|
-
6. **Do the testimonials sound like they were written by the same person?** If yes, rewrite with different voices, lengths, and structures.
|
|
455
|
-
7. **Would a HubSpot marketer on their third coffee read this and think "yeah, that sounds like us"?** That's the bar.
|
|
641
|
+
* Sounds natural when read aloud
|
|
642
|
+
* Varies sentence structure
|
|
643
|
+
* Uses specific details
|
|
644
|
+
* Maintains appropriate tone
|
|
456
645
|
|
|
457
646
|
---
|
|
458
647
|
|
|
459
|
-
|
|
648
|
+
## The Final Sniff Test
|
|
649
|
+
|
|
650
|
+
After generating any copy, read it once and ask:
|
|
651
|
+
|
|
652
|
+
1. Could I picture a specific human saying this out loud? If not, rewrite.
|
|
653
|
+
2. Can I see/touch/count the thing being described? If not, make it concrete.
|
|
654
|
+
3. Does every sentence sound roughly the same length? If yes, vary it.
|
|
655
|
+
4. Are there more than zero em dashes? If yes, remove them all.
|
|
656
|
+
5. Does the page have any word from the HARD BANNED list? If yes, swap it.
|
|
657
|
+
6. Do the testimonials sound like they were written by the same person? If yes, rewrite with different voices, lengths, and structures.
|
|
658
|
+
7. Does it have a pulse? Not just clean, but alive. If it reads like a press release, add voice.
|
|
@@ -17,15 +17,24 @@ TBD — who reads this content and what do they come for?
|
|
|
17
17
|
## Primary CTA
|
|
18
18
|
TBD — typically "Subscribe" or "Read latest". Secondary: "Browse by topic".
|
|
19
19
|
|
|
20
|
-
##
|
|
21
|
-
1. **
|
|
22
|
-
2. **topic-
|
|
23
|
-
3. **
|
|
24
|
-
4. **
|
|
25
|
-
5. **
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
20
|
+
## Blog Listing Modules
|
|
21
|
+
1. **blog-header** — blog name, tagline, hero area
|
|
22
|
+
2. **topic-filter** — pill/chip navigation for categories (uses `blog_topics()` HubL)
|
|
23
|
+
3. **post-grid** — card grid with `{% for content in contents %}` loop, pagination
|
|
24
|
+
4. **newsletter-signup** — email capture with value-prop copy
|
|
25
|
+
5. **popular-posts** — sidebar or section with evergreen / most-read posts (uses `blog_recent_posts()`)
|
|
26
|
+
|
|
27
|
+
## Blog Post Modules
|
|
28
|
+
1. **blog-post-header** — title (`content.name`), featured image, author avatar, date, tags
|
|
29
|
+
2. **blog-post-body** — wraps `{{ content.post_body }}` with reading-optimized typography (18-20px body, 720px max-width)
|
|
30
|
+
3. **author-bio** — author card with `content.author.avatar`, bio, social links
|
|
31
|
+
4. **related-posts** — 3 related post cards (uses `blog_recent_posts()`)
|
|
32
|
+
5. **share-bar** — social sharing buttons (uses `{% blog_social_sharing %}` or custom links)
|
|
33
|
+
|
|
34
|
+
## HubSpot Blog Variables
|
|
35
|
+
- Post: `content.name`, `content.post_body`, `content.featured_image`, `content.publish_date`, `content.blog_post_author`, `content.tag_list`
|
|
36
|
+
- Listing: `{% for content in contents %}`, `group.public_title`, pagination via `blog_page_link()`
|
|
37
|
+
- Meta: `host_template_types: ["BLOG_POST"]` or `["BLOG_LISTING"]` in meta.json
|
|
29
38
|
|
|
30
39
|
## Brand & Tone
|
|
31
40
|
TBD — magazine/editorial, technical/research, conversational/personal
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: email-announcement
|
|
3
|
+
label: Product Announcement
|
|
4
|
+
description: New feature, product update, or company news announcement
|
|
5
|
+
icon: megaphone
|
|
6
|
+
order: 110
|
|
7
|
+
contentType: email
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Product Announcement Email
|
|
11
|
+
|
|
12
|
+
## Goal
|
|
13
|
+
Announce a new feature, product update, or company milestone. Drive recipients to try, learn about, or engage with the announcement.
|
|
14
|
+
|
|
15
|
+
## Audience
|
|
16
|
+
TBD — existing customers, all subscribers, specific segment?
|
|
17
|
+
|
|
18
|
+
## Primary CTA
|
|
19
|
+
TBD — common patterns: "Try It Now", "See What's New", "Read the Full Story".
|
|
20
|
+
|
|
21
|
+
## Sections / Modules
|
|
22
|
+
1. **preheader** — hidden inbox preview text
|
|
23
|
+
2. **header** — logo, optional "What's New" badge
|
|
24
|
+
3. **hero** — bold headline announcing the update, hero image or product screenshot
|
|
25
|
+
4. **features** — 3-4 key benefits of the update (not features list — what it means for them)
|
|
26
|
+
5. **cta-block** — primary CTA to try or learn more
|
|
27
|
+
6. **footer** — unsubscribe link, physical address, social links
|
|
28
|
+
|
|
29
|
+
## Subject Line & Preheader
|
|
30
|
+
- Subject: TBD — e.g., "We just shipped [feature]. Here's why it matters."
|
|
31
|
+
- Preheader: TBD — extends subject, 40-90 chars
|
|
32
|
+
|
|
33
|
+
## Brand & Tone
|
|
34
|
+
TBD — excited but grounded? Technical and precise? Casual and conversational?
|
|
35
|
+
|
|
36
|
+
## Open questions
|
|
37
|
+
- [ ] What is being announced (feature, product, update, milestone)?
|
|
38
|
+
- [ ] What are the top 3 benefits for the recipient?
|
|
39
|
+
- [ ] Is there a visual (screenshot, illustration, demo GIF)?
|
|
40
|
+
- [ ] Is this available to everyone or a specific tier/segment?
|
|
41
|
+
- [ ] Is there a deadline or urgency element?
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: email-event-invite
|
|
3
|
+
label: Event Invitation
|
|
4
|
+
description: Webinar, conference, meetup, or launch event invite
|
|
5
|
+
icon: calendar
|
|
6
|
+
order: 130
|
|
7
|
+
contentType: email
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Event Invitation Email
|
|
11
|
+
|
|
12
|
+
## Goal
|
|
13
|
+
Drive registrations or RSVPs for an event. Communicate the value of attending clearly enough that recipients act within one read.
|
|
14
|
+
|
|
15
|
+
## Audience
|
|
16
|
+
TBD — existing customers, prospects, community, specific segment?
|
|
17
|
+
|
|
18
|
+
## Primary CTA
|
|
19
|
+
TBD — common patterns: "Register Now", "Save Your Spot", "RSVP".
|
|
20
|
+
|
|
21
|
+
## Sections / Modules
|
|
22
|
+
1. **preheader** — hidden inbox preview text
|
|
23
|
+
2. **header** — logo, optional "You're Invited" badge
|
|
24
|
+
3. **hero** — event name headline, date/time/location prominently displayed, hero image or event banner
|
|
25
|
+
4. **details** — what the event covers, who should attend, what they'll learn (2-3 bullet points)
|
|
26
|
+
5. **speakers** — speaker/host bios with headshots (if applicable)
|
|
27
|
+
6. **cta-block** — single "Register" CTA with urgency note (limited spots, early-bird deadline)
|
|
28
|
+
7. **footer** — unsubscribe link, physical address, calendar add link
|
|
29
|
+
|
|
30
|
+
## Subject Line & Preheader
|
|
31
|
+
- Subject: TBD — e.g., "Join us March 15: [Event Topic] with [Speaker]"
|
|
32
|
+
- Preheader: TBD — extends subject, 40-90 chars
|
|
33
|
+
|
|
34
|
+
## Brand & Tone
|
|
35
|
+
TBD — professional and authoritative? Casual and community-driven? Exclusive and premium?
|
|
36
|
+
|
|
37
|
+
## Open questions
|
|
38
|
+
- [ ] Event name, date, time (with timezone), and format (in-person, virtual, hybrid)?
|
|
39
|
+
- [ ] Location or platform (Zoom, venue address)?
|
|
40
|
+
- [ ] Who are the speakers or hosts?
|
|
41
|
+
- [ ] What will attendees learn or gain?
|
|
42
|
+
- [ ] Is there a capacity limit or registration deadline?
|
|
43
|
+
- [ ] Is there an early-bird or free-tier pricing?
|