Becoming the WordPress Evangelist I Needed
🔗 **Source:** [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/)
> [!note]+ Document Notes
> tags: [WordPress, Community, DevRel]
> author: [MISSING]
> source: iconick.io
> reference: [https://iconick.io/wordpress-evangelist/]
> date created:
>
> # 🏷️ Title: Becoming the WordPress Evangelist I Needed
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- The author embraces a product evangelist role for WordPress.
- The piece argues for optimism amid community negativity and AI shifts.
- Stakeholders include WordPress users, contributors, and plugin authors.
- Risks include perceived “toxic positivity” and uneven follow-through.
- Bottom line: consistent, people-first evangelism can sustain engagement.
## 📖 Main Content
- The author realizes they already act as a WordPress evangelist.
- A friend flags inconsistent engagement; the author commits to steadiness.
- The AI wave makes momentum-building timely and necessary.
- The plan includes blogging, amplifying peers, and honest plugin reviews.
- The stance rejects cynicism while not denying problems.
- The core claim centers people over code.
### 🗒️ Notes
### [H1] Author identifies as product evangelist now
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “Dave Winer… used a phrase I’d never heard before: product evangelist.”
Role framing matters for DevRel planning and goals.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #articleseed ID:rw_[MISSING]
### [H2] Inconsistency acknowledged; commitment follows
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “I’m mercurial… I drift in and out of the WordPress community…”
Sets a baseline problem and a pledge to show up.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref ID:rw_[MISSING]
### [H3] Optimism counters community negativity
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “My optimism sounds like ‘toxic positivity.’… There’s already so much negativity…”
Positions positivity as strategic, not naive.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #articleseed ID:rw_[MISSING]
### [H4] Evangelism actions: blog, amplify, review
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “Blogging… Amplifying others… Checking out new plugins and leaving real reviews…”
Concrete activities enable repeatable DevRel loops.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #articleseed ID:rw_[MISSING]
### [H5] People are WordPress’s best feature
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “The best parts of WordPress aren’t the code or the plugins—it’s the people…”
Centers community as primary value driver.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #share ID:rw_[MISSING]
## 📚 References
- [WordPress.org](https://wordpress.org/)
- [What is a product evangelist?](https://www.gartner.com/en/marketing/insights/articles/what-is-a-brand-evangelist) (context)
- [Dave Winer](http://scripting.com/) (mentioned; attribution context)
- [Responsible AI in OSS overview](https://opensource.guide/) (contextual OSS guidance)
## 🗣️ Paraphrase
- The author accepts a WordPress evangelist identity and commits to consistency.
- They propose visible, positive actions that highlight people and progress.
## 📰 Newsletter
- This week: a call for steady WordPress evangelism.
- Highlights: blog shipping, amplifying builders, and candid plugin reviews.
- The author rejects cynicism while facing AI-era change.
- Try this: share one community win and review a plugin you used.
- Links: check [WordPress.org](https://wordpress.org/) and follow [Dave Winer](http://scripting.com/).
## ✅ Action Items
#### DevRel
- Publish a weekly “What’s Working in WP” post with metrics.
- Run monthly plugin review streams with actionable takeaways.
- Create a contributor shoutout thread and track engagements.
- Define evangelism KPIs: posts, reach, conversions, NPS.
#### OSPO
- Draft an upstream contribution policy and review cadence.
- Propose an open governance charter template for pilots.
- Set a compliance and SBOM training calendar.
#### Community
- Host “stay engaged” office hours for returning contributors.
- Launch a peer amplification rota across social channels.
- Publish a transparent community wins dashboard.
#### WordPress
- Core: propose a newcomer-friendly triage rotation.
- Playground: record reproducible-bug tutorials.
- Training: add “evangelism basics” learning path.
- Marketing: feature monthly contributor spotlights.
- Documentation: add examples-first plugin review guide.
#### The WPOCC
- Launch microgrants for contributor retention programs.
- Fund community documentation sprints with milestones.
- Publish ledger updates and impact reports quarterly.
### FAIR
- Ship a minimal provenance and signatures policy draft.
- Define transparent funding covenants with sunset clauses.
- Package governance scorecards for community pilots.
## 🧪 Hypotheses
- Regular evangelism posts increase newcomer retention by 15% quarter-over-quarter.
- Peer amplification improves plugin review readership by 25%.
- Positive framing reduces public churn statements by 10%.
- Highlighting people increases volunteer hours by 12%.
### 📊 Methodology
- A/B test newsletter formats; track CTR and retention.
- Time-series analyze review traffic and conversions.
- Monitor churn signals across community forums.
- Survey volunteers on motivation and time donated.
### ❓ Questions
- Which evangelism metrics predict sustained contribution?
- How to separate positivity from problem denial?
- What cadence keeps morale high without burnout?
### 🔮 Future Research
- Study AI-era onboarding friction in WordPress.
- Model incentives that retain maintainers long-term.
- Evaluate microgrant ROI on contributor hours.
### 💡 Implications
- Structured evangelism can stabilize community health.
- People-first storytelling may outperform feature lists.
- Transparent funding links praise to tangible outcomes.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid Grade ~7–9.
#### 👀 Visual learners
- Present: lists; structure.
- Improve: diagrams of evangelism loops.
#### 🔊 Aural learners
- Present: none.
- Improve: 3–5 minute audio recap.
#### 🗣️ Verbal learners
- Present: clear definitions and commitments.
- Improve: glossary of roles and metrics.
#### 🧩 Kinesthetic learners
- Present: actionable steps.
- Improve: checklists and labs with templates.
#### 🧠 Logical learners
- Present: bullet logic.
- Improve: KPIs, funnels, and RACIs.
#### 🧑🤝🧑 Social learners
- Present: community call-in.
- Improve: cohort peer circles.
#### 🧘♀️ Solitary learners
- Present: reflective framing.
- Improve: self-audit worksheet.
#### 🌿 Naturalistic learners
- Present: ecosystem metaphor.
- Improve: lifecycle views of projects.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: headings and lists.
- Improve: ensure alt text where images exist.
#### Keyboard navigation
- Present: likely standard blog nav.
- Improve: verify skip links and focus states.
#### Contrast and readability
- Present: check 4.5:1 minimum.
- Improve: validate line-height and spacing.
#### Text resizing and reflow
- Present: responsive layout expected.
- Improve: test 200% zoom and reflow.
#### Media and captions
- Present: text only.
- Improve: add audio and captions if media added.
#### Forms and interactions
- Present: comments form considerations.
- Improve: labels, errors, target size.
#### Standards reference
- Map to WCAG 2.2 AA criteria.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: general community framing.
- Improve: global examples and multilingual links.
#### Inclusive language
- Present: welcoming tone.
- Improve: plain-language summaries and glossaries.
#### Neurodiversity support
- Present: chunked bullets.
- Improve: consistent icons and patterning.
#### Representation
- Present: people-centered message.
- Improve: showcase diverse contributor stories.
#### Psychological safety
- Present: respectful and supportive.
- Improve: share community guidelines and escalation paths.
### ✅ Logical Validity
#### Strong reasoning
- Inductive link between positivity and retention [H3], [H5].
- Actionable plan supports claims [H4].
#### Fallacies
- Risk of hasty generalization on positivity impact; temper with data.
- Fix by adding measurable KPIs and controls.
#### Tone of voice
- Candid, optimistic, and invitational.
### 🛡️ DARVO Analysis
- Deny: does not deny problems; reframes them.
- Attack: no attacks on critics; acknowledges concerns.
- Reverse victim/offender: none observed.
## 🎯 Conclusion
- The article commits to steady, people-first WordPress evangelism.
- Next steps: publish, amplify, review, and measure outcomes.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: **H3**.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] Author identifies as product evangelist now
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed .
> “Dave Winer… used a phrase I’d never heard before: product evangelist.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://iconick.io/wordpress-evangelist/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Inconsistency acknowledged; commitment follows
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/)
> “I’m mercurial… I drift in and out of the WordPress community…”
Two lines: context and use.
[view highlight](https://iconick.io/wordpress-evangelist/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: **H4**.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Evangelism consistency increases community retention
- Condition: weekly posts and monthly reviews for 2 quarters.
- Links: [[DevRel-Metrics]] [[Contributor-Retention]]
#### [Z2] People-first framing strengthens contributor motivation
- Condition: regular spotlights and acknowledgment loops.
- Links: [[Community-Health]] [[Recognition-Programs]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Draft “What’s Working in WP” v1 — context/https://iconick.io/wordpress-evangelist/ #fleeting #inbox
- [F2] Plan plugin review livestream outline — context/https://iconick.io/wordpress-evangelist/ #fleeting #inbox
- [F3] Build contributor spotlight template — context/https://iconick.io/wordpress-evangelist/ #fleeting #inbox
---
<!-- deep-read:sections end -->
[[3. Resources/Readwise/Full Document Contents/Articles/Becoming the WordPress Evangelist I Needed|Full Document Contents]]
## Document Notes
---
tags: #WordPress #Community #DevRel
author: [MISSING]
source: iconick.io
reference: [https://iconick.io/wordpress-evangelist/]
date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
---
# 🏷️ Title: Becoming the WordPress Evangelist I Needed
## 🧭 Table of Contents
- [[#📝 Summary]]
- [[#📖 Main Content]]
- [[#🗒️ Notes]]
- [[#📚 References]]
- [[#🗣️ Paraphrase]]
- [[#📰 Newsletter]]
- [[#✅ Action Items]]
- [[#🧪 Hypotheses]]
- [[#📊 Methodology]]
- [[#❓ Questions]]
- [[#🔮 Future Research]]
- [[#💡 Implications]]
- [[#🧠 Learning Styles Assessment]]
- [[#📊 Accessibility Assessment]]
- [[#🌍 DEIB Assessment]]
- [[#✅ Logical Validity]]
- [[#🛡️ DARVO Analysis]]
- [[#🎯 Conclusion]]
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- The author embraces a product evangelist role for WordPress.
- The piece argues for optimism amid community negativity and AI shifts.
- Stakeholders include WordPress users, contributors, and plugin authors.
- Risks include perceived “toxic positivity” and uneven follow-through.
- Bottom line: consistent, people-first evangelism can sustain engagement.
## 📖 Main Content
- The author realizes they already act as a WordPress evangelist.
- A friend flags inconsistent engagement; the author commits to steadiness.
- The AI wave makes momentum-building timely and necessary.
- The plan includes blogging, amplifying peers, and honest plugin reviews.
- The stance rejects cynicism while not denying problems.
- The core claim centers people over code.
### 🗒️ Notes
### [H1] Author identifies as product evangelist now
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “Dave Winer… used a phrase I’d never heard before: product evangelist.”
Role framing matters for DevRel planning and goals.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #articleseed ID:rw_[MISSING]
### [H2] Inconsistency acknowledged; commitment follows
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “I’m mercurial… I drift in and out of the WordPress community…”
Sets a baseline problem and a pledge to show up.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref ID:rw_[MISSING]
### [H3] Optimism counters community negativity
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “My optimism sounds like ‘toxic positivity.’… There’s already so much negativity…”
Positions positivity as strategic, not naive.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #articleseed ID:rw_[MISSING]
### [H4] Evangelism actions: blog, amplify, review
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “Blogging… Amplifying others… Checking out new plugins and leaving real reviews…”
Concrete activities enable repeatable DevRel loops.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #articleseed ID:rw_[MISSING]
### [H5] People are WordPress’s best feature
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “The best parts of WordPress aren’t the code or the plugins—it’s the people…”
Centers community as primary value driver.
[view highlight](https://iconick.io/wordpress-evangelist/) #xref #share ID:rw_[MISSING]
## 📚 References
- [WordPress.org](https://wordpress.org/)
- [What is a product evangelist?](https://www.gartner.com/en/marketing/insights/articles/what-is-a-brand-evangelist) (context)
- [Dave Winer](http://scripting.com/) (mentioned; attribution context)
- [Responsible AI in OSS overview](https://opensource.guide/) (contextual OSS guidance)
## 🗣️ Paraphrase
- The author accepts a WordPress evangelist identity and commits to consistency.
- They propose visible, positive actions that highlight people and progress.
## 📰 Newsletter
- This week: a call for steady WordPress evangelism.
- Highlights: blog shipping, amplifying builders, and candid plugin reviews.
- The author rejects cynicism while facing AI-era change.
- Try this: share one community win and review a plugin you used.
- Links: check [WordPress.org](https://wordpress.org/) and follow [Dave Winer](http://scripting.com/).
## ✅ Action Items
#### DevRel
- Publish a weekly “What’s Working in WP” post with metrics.
- Run monthly plugin review streams with actionable takeaways.
- Create a contributor shoutout thread and track engagements.
- Define evangelism KPIs: posts, reach, conversions, NPS.
#### OSPO
- Draft an upstream contribution policy and review cadence.
- Propose an open governance charter template for pilots.
- Set a compliance and SBOM training calendar.
#### Community
- Host “stay engaged” office hours for returning contributors.
- Launch a peer amplification rota across social channels.
- Publish a transparent community wins dashboard.
#### WordPress
- Core: propose a newcomer-friendly triage rotation.
- Playground: record reproducible-bug tutorials.
- Training: add “evangelism basics” learning path.
- Marketing: feature monthly contributor spotlights.
- Documentation: add examples-first plugin review guide.
#### The WPCC
- Launch microgrants for contributor retention programs.
- Fund community documentation sprints with milestones.
- Publish ledger updates and impact reports quarterly.
### FAIR
- Ship a minimal provenance and signatures policy draft.
- Define transparent funding covenants with sunset clauses.
- Package governance scorecards for community pilots.
## 🧪 Hypotheses
- Regular evangelism posts increase newcomer retention by 15% quarter-over-quarter.
- Peer amplification improves plugin review readership by 25%.
- Positive framing reduces public churn statements by 10%.
- Highlighting people increases volunteer hours by 12%.
### 📊 Methodology
- A/B test newsletter formats; track CTR and retention.
- Time-series analyze review traffic and conversions.
- Monitor churn signals across community forums.
- Survey volunteers on motivation and time donated.
### ❓ Questions
- Which evangelism metrics predict sustained contribution?
- How to separate positivity from problem denial?
- What cadence keeps morale high without burnout?
### 🔮 Future Research
- Study AI-era onboarding friction in WordPress.
- Model incentives that retain maintainers long-term.
- Evaluate microgrant ROI on contributor hours.
### 💡 Implications
- Structured evangelism can stabilize community health.
- People-first storytelling may outperform feature lists.
- Transparent funding links praise to tangible outcomes.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid Grade ~7–9.
#### 👀 Visual learners
- Present: lists; structure.
- Improve: diagrams of evangelism loops.
#### 🔊 Aural learners
- Present: none.
- Improve: 3–5 minute audio recap.
#### 🗣️ Verbal learners
- Present: clear definitions and commitments.
- Improve: glossary of roles and metrics.
#### 🧩 Kinesthetic learners
- Present: actionable steps.
- Improve: checklists and labs with templates.
#### 🧠 Logical learners
- Present: bullet logic.
- Improve: KPIs, funnels, and RACIs.
#### 🧑🤝🧑 Social learners
- Present: community call-in.
- Improve: cohort peer circles.
#### 🧘♀️ Solitary learners
- Present: reflective framing.
- Improve: self-audit worksheet.
#### 🌿 Naturalistic learners
- Present: ecosystem metaphor.
- Improve: lifecycle views of projects.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: headings and lists.
- Improve: ensure alt text where images exist.
#### Keyboard navigation
- Present: likely standard blog nav.
- Improve: verify skip links and focus states.
#### Contrast and readability
- Present: check 4.5:1 minimum.
- Improve: validate line-height and spacing.
#### Text resizing and reflow
- Present: responsive layout expected.
- Improve: test 200% zoom and reflow.
#### Media and captions
- Present: text only.
- Improve: add audio and captions if media added.
#### Forms and interactions
- Present: comments form considerations.
- Improve: labels, errors, target size.
#### Standards reference
- Map to WCAG 2.2 AA criteria.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: general community framing.
- Improve: global examples and multilingual links.
#### Inclusive language
- Present: welcoming tone.
- Improve: plain-language summaries and glossaries.
#### Neurodiversity support
- Present: chunked bullets.
- Improve: consistent icons and patterning.
#### Representation
- Present: people-centered message.
- Improve: showcase diverse contributor stories.
#### Psychological safety
- Present: respectful and supportive.
- Improve: share community guidelines and escalation paths.
### ✅ Logical Validity
#### Strong reasoning
- Inductive link between positivity and retention [H3], [H5].
- Actionable plan supports claims [H4].
#### Fallacies
- Risk of hasty generalization on positivity impact; temper with data.
- Fix by adding measurable KPIs and controls.
#### Tone of voice
- Candid, optimistic, and invitational.
### 🛡️ DARVO Analysis
- Deny: does not deny problems; reframes them.
- Attack: no attacks on critics; acknowledges concerns.
- Reverse victim/offender: none observed.
## 🎯 Conclusion
- The article commits to steady, people-first WordPress evangelism.
- Next steps: publish, amplify, review, and measure outcomes.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: **H3**.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] Author identifies as product evangelist now
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/) by [[iconik]] via [[iconick.io]]. Published 2025-10-05. Accessed {{date:YYYY-MM-DD}}.
> “Dave Winer… used a phrase I’d never heard before: product evangelist.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://iconick.io/wordpress-evangelist/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Inconsistency acknowledged; commitment follows
> [!quote] [Becoming the WordPress Evangelist I Needed](https://iconick.io/wordpress-evangelist/)
> “I’m mercurial… I drift in and out of the WordPress community…”
Two lines: context and use.
[view highlight](https://iconick.io/wordpress-evangelist/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: **H4**.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Evangelism consistency increases community retention
- Condition: weekly posts and monthly reviews for 2 quarters.
- Links: [[DevRel-Metrics]] [[Contributor-Retention]]
#### [Z2] People-first framing strengthens contributor motivation
- Condition: regular spotlights and acknowledgment loops.
- Links: [[Community-Health]] [[Recognition-Programs]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Draft “What’s Working in WP” v1 — context/https://iconick.io/wordpress-evangelist/ #fleeting #inbox
- [F2] Plan plugin review livestream outline — context/https://iconick.io/wordpress-evangelist/ #fleeting #inbox
- [F3] Build contributor spotlight template — context/https://iconick.io/wordpress-evangelist/ #fleeting #inbox
---
## 🧰 Template Library (paste into Note Refactor → Refactored Note Template)
<!-- Copy ONE template at a time into the plugin before running each batch. -->
### 📝 Fleeting — Refactored Note Template (Konik-ready)
---
type: fleeting
status: inbox
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
process_by: {{date:YYYY-MM-DD}} # review within 24–48 hrs
source_title: [MISSING]
source_link:
author: [MISSING]
source_type: article|paper|video|podcast|thread
reading_stage: inspectional|analytical|syntopical
project:
tags: #fleeting #inbox
---
# 📝 Fleeting Note — {{title}}
## 🧠 One-liner (my words)
- State the single idea in one short sentence.
## 🧭 Context & cue
- Where did this arise? Page/timecode/speaker.
- Trigger: quote, data point, claim, or question.
## 🧪 Adler checks (quick)
- What is this about as a whole?
- What is said in detail, and how?
- Is it true? Evidence for or against?
- So what? Impact or next move.
## 🔎 Bias & reliability snapshot
- Possible bias or framing?
- What evidence would change my view?
## 🧩 Konik bridge
- Draft a claim header for promotion.
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{source_link}}) by [[{{author}}]]. Accessed {{date:YYYY-MM-DD}}.
> “Short quote under ~25 words.”
One line on why this matters.
[view highlight]({{source_link}}) #xref ID:rw_[MISSING]
## 🧰 Next moves (pick 1–2)
- [ ] Promote to *Literature* with citation.
- [ ] Draft *Atomic* claim from [H1].
- [ ] Park as testable question.
## ✅ Processing checklist
- [ ] Rewrote in my words.
- [ ] Decided: trash | keep | convert.
- [ ] Linked to at least one related note.
- [ ] Tagged and moved out of inbox.
---
### 📚 Literature — Refactored Note Template (Konik-ready)
---
type: literature
status: draft
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
adler_level: inspectional|analytical|syntopical
reading_stage: inspectional|analytical|syntopical
source_title: [MISSING]
author: [MISSING]
year:
publisher_or_journal:
edition_or_volume:
doi:
url:
accessed: {{date:YYYY-MM-DD}}
citekey:
project:
tags: #literature #reading
---
# 📚 Literature Note — {{title}}
## 🧰 Action Inbox
- [H1] Short action — context/{{url}} #articleseed
- [H2] Short action — context/{{url}} #xref
- [H3] Short action — context/{{url}} #share
## 🧭 Bib Capsule
- Title, author, year, venue, and link.
- One-line scope: what the work attempts.
## 🧠 Author’s Thesis (their words)
- Core claim briefly. Include page/timecode.
## 🧩 Key Arguments
- Argument A — method/evidence — page/time.
- Argument B — method/evidence — page/time.
- Argument C — method/evidence — page/time.
## 🧪 Evaluation (Adler)
- What is this about as a whole?
- How is it argued? Fairly and clearly?
- Is it true or plausible? Why?
- So what? Practical or theoretical impact.
## 🗒️ Notes (Konik CEE units)
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H2) #xref ID:rw_[MISSING]
## 🔖 Zettel Candidates
#### [Z1] 5–10-word present-tense claim
- One-line context and page/time.
#### [Z2] 5–10-word present-tense claim
- One-line context and page/time.
## 🏷️ Tag Coverage
#articleseed: 3 • #xref: 5 • #share: 1 • #bmf: 0 • #addendum: 0
## ✅ Processing Checklist
- [ ] Thesis captured in my words.
- [ ] 1–3 Zettel candidates drafted.
- [ ] Action Inbox pruned to high-signal items.
- [ ] Cross-links added and filed.
---
### 🔖 Atomic (Zettel) — Refactored Note Template (Konik-ready)
---
type: atomic
id: {{date:YYYYMMDDHHmm}}-{{title}}
status: evergreen
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
origin: reading|thinking|experiment
proof_state: conjecture|working|supported|refuted
source_literature: [[Source-Literature-Note]]
citekey:
project:
tags: #zettel #idea
---
# 🔖 {{title}} <!-- 5–10 words, present tense, specific -->
## 🧠 Claim
- One idea only. Clear and testable.
## 🧾 Evidence & Pointers (Konik)
- [H#] from [[{{source_literature}}]] — page/time — brief rationale.
- ID:rw_[MISSING] — link to highlight or dataset.
> [!quote] Evidence snippet (≤25 words) if essential.
> Cite page/time. Keep it minimal.
## 🔍 Scope & Conditions
- When this holds. Boundaries and exceptions.
## 🔗 Links
- Broader: [[Parent-Concept]]
- Narrower: [[Specific-Case]]
- Related: [[Parallel-Idea]]
## 🧪 Tests / Falsifiers
- One check that could disconfirm the claim.
- Simple study or observation plan.
## 🧰 Implications
- Practice, policy, or design moves in one line each.
## 🔙 Backlinks
- From: [[{{source_literature}}]] • Context line.
## ✅ Maintenance
- [ ] Links in and out.
- [ ] Title still precise?
- [ ] Proof state updated.
## Highlights
- **product evangelist**. Someone who hypes things up, who gets genuinely excited and spreads that energy to others. ([View Highlight](https://read.readwise.io/read/01k6txts3j3b6as6e4z6y22dpv))
- I drift in and out of the WordPress community when I get discouraged or bored. I disappear when the negativity gets too heavy or when I lose that spark. ([View Highlight](https://read.readwise.io/read/01k6txv4kd9kafwc1wetpnq5ms))
- Someone told me this week that my optimism sounds like “toxic positivity.” ([View Highlight](https://read.readwise.io/read/01k6txvmn3fpcxx4mge6gjmbc5))
- • **Blogging about things that genuinely excite me** about WordPress and where we’re headed
• **Amplifying others doing cool work** — reblogging, sharing, shouting about the awesome stuff happening in our community
• **Checking out new plugins and leaving real reviews** for the things I think are worth your time ([View Highlight](https://read.readwise.io/read/01k6txvryvsw9cz7cab0sm7mj0))
## 🌱 Spawned Notes
- [[Lit · Author identifies as product evangelist now]]
- [[Lit · Inconsistency acknowledged commitment follows]]
- [[Zet · Evangelism consistency increases community retention]]
- [[Zet · People-first framing strengthens contributor motivation]]
- [[Flt · Draft Whats Working in WP v1]]
- [[Flt · Plan plugin review livestream outline]]
- [[Flt · Build contributor spotlight template]]