open/linkedin-studio
1
0
Fork 0
Code Issues Releases 1 Activity

fix(linkedin-studio): S29c terminology-scrub — "thought leadership" → neutral (references/)

Browse source 
Third sub-pass of the S29 plugin-wide terminology scrub: the banned brand phrase
"thought leadership" (FORM A) removed from the reference-doc surface — the largest pass
(2x S29a/S29b). 34 edits across 15 reference files. Vocabulary consistent with S29a/S29b:
"thought leadership angle(s)" -> "content angle(s)"; "thought leadership" (positioning/practice)
-> "authority ..."; content-type labels -> "authority content / authority posts"; the whole
"Value Test" family -> "Authority Value Test".

Established cross-pass equivalents closed: glossary:229 "Thought Leadership Value Test" ->
"Authority Value Test" (closes the S29b cross-directory naming gap); glossary:29 "8 universal
thought leadership angles" -> "content angles"; engagement-frameworks:137 "Standard Thought
Leadership Structure" -> "Standard Post Structure" (matches S29a post:98).

S29e filename locked this session: thought-leadership-angles.md -> content-angles.md (operator-
chosen). The canonical file's in-file title/headers scrubbed now for consistency (H1 ->
"# Content Angles"; "## The Authority Value Test"; "### Step 3: Test For Authority Value");
the file rename + all 20 pointers remain S29e (atomic).

Judgment-calls (operator-approved): thought-leadership-angles:212 "disguised as thought
leadership" -> "expertise" (S29b vocab); linkedin-formats:295 -> "Text-based content" (avoids
authority...authority echo); linkedin-visual-style:3 -> "For building authority,"; ai-content-
framework:380 "main LinkedIn thought leadership skill" -> "content skill" (avoids awkward
"authority skill"). Kept by design: video-strategy-guide:429 ironic quote; video-strategy-
guide:532 "TL;DW" false positive (too long, didn't watch).

Scope (operator-locked, inherits S29a/S29b): FORM A only. FORM B ("thought leader(s)" as role,
references = 4) untouched. The 3 thought-leadership-angles.md filename pointers in references/
deferred to S29e.

Verify: FORM A in references/ = only the kept ironic quote (video:429); canonical file in-file
FORM A = NONE; FORM B unchanged (4); filename pointers unchanged (3); no anchor links to changed
headers; gate 81/0/0; counts 29/19/26/6 + v0.5.0 unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qgzo6rxthw7KuxHjn5vyE
This commit is contained in:
Kjell Tore Guttormsen 2026-06-20 05:44:05 +02:00
commit 25b356fc5c
15 changed files with 34 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

8
references/linkedin-visual-style.md
View file

@ -1,10 +1,10 @@
# LinkedIn Visual Style Guide
Visual content on LinkedIn follows different rules than Instagram or Twitter. For thought leadership, text-first content consistently outperforms image-heavy posts. This guide defines when and how to use visuals strategically.
Visual content on LinkedIn follows different rules than Instagram or Twitter. For building authority, text-first content consistently outperforms image-heavy posts. This guide defines when and how to use visuals strategically.
## The Text-First Principle
LinkedIn rewards dwell time and conversation, not visual impressions. Pure text posts with strong hooks generate more comments and shares than image posts in the thought leadership niche.
LinkedIn rewards dwell time and conversation, not visual impressions. Pure text posts with strong hooks generate more comments and shares than image posts in the authority niche.
**When text-only wins:**
- Personal stories and lessons learned
@ -79,7 +79,7 @@ LinkedIn users scroll fast. Your visual has 1-2 seconds to communicate its value
## When to Use Each Visual Format
### No Image (Text-Only Post)
**Best for:** Thought leadership, stories, opinions, quick tips
**Best for:** Authority content, stories, opinions, quick tips
**Engagement pattern:** Highest comment rates, strong for dwell time
**Use when:** The value is in the words, not in showing something
@ -120,7 +120,7 @@ Before adding a visual, ask:
1. **Does this need to be seen, not just read?** If no → text-only
2. **Does the visual add information the text doesn't?** If no → text-only
3. **Would someone save this image for reference?** If yes → carousel or infographic
4. **Am I adding an image just because "posts with images get more engagement"?** → Stop. That's a myth for thought leadership content
4. **Am I adding an image just because "posts with images get more engagement"?** → Stop. That's a myth for authority content
## Tools by Skill Level