Slurp Fixed Saving Web Articles to Obsidian
🔗 **Source:** [Slurp Fixed Saving Web Articles to Obsidian](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/)
> [!note]+ Document Notes
> ```markdown
>
> ---
> tags: [obsidian, plugins, read-it-later]
> author: Curtis McHale
> source: curtismchale.ca
> reference: [https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/]
> date created:
>
> ---
>
> # 🏷️ Title: Slurp Fixed Saving Web Articles to Obsidian
>
<!-- 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
- What happened.
- The author replaced broken Obsidian capture tools (ReadItLater, Obsidian Web Clipper) with the Slurp plugin to save web articles reliably.
- Why it matters.
- Stable capture is foundational for any Obsidian-based reading, research, or PKM workflow.
- Key stakeholders.
- Obsidian users, plugin maintainers, knowledge workers who save web content.
- Risks and tradeoffs.
- Depends on a single community plugin; browser extensions are still in progress; bookmarklet requires some manual interaction.
- Bottom line.
- Slurp provides a simpler, more reliable “save to Obsidian” flow today, with a likely better UX once official browser extensions land.
## 📖 Main Content
- Explain the core arguments in plain language.
- Previously, saving web pages into Obsidian required two tools that were unreliable. The author searched the community plugins for “Read Later,” found Slurp, and discovered it solved the capture issues on the first try.
- Slurp lets you configure where notes land (e.g., `Sources/Clippings`) and how properties and tags are handled, then save any page by copying its URL, running the Slurp command from Obsidian’s command palette, pasting the link, and jumping directly to the new note.
- For faster capture, Slurp offers a JavaScript bookmarklet today and is developing full browser extensions, which should reduce friction further.
- Add sourced context and define terms.
- Obsidian is a local-first Markdown note app; its ecosystem depends heavily on plugins to extend core behavior, including web clipping.
- A bookmarklet is a browser bookmark whose “URL” is JavaScript; it runs in-page to perform an action, here triggering Slurp via Obsidian.
- Note uncertainties or contested claims.
- The article reports personal experience, not benchmarks across many sites or edge cases.
- Stability over time depends on Slurp’s maintenance and Obsidian/plugin API changes.
### 🗒️ Notes
- The author’s previous stack (ReadItLater + Obsidian Web Clipper) required saving pages twice and still didn’t consistently capture the desired content.
- A search for “Read Later” in Obsidian’s community plugin manager surfaced Slurp, which immediately fixed the reliability problem for the author.
- Key configuration: setting the destination folder (e.g., `Sources/Clippings`) to integrate with an existing vault structure; optional tweaks include property ordering and tag parsing.
- The author prefers “Tag Notes” over inline tags, so Slurp’s tag-based features are left off, signaling that Slurp works even in tag-minimal workflows.
- Capture flow:
- Navigate to a target web page.
- Copy the URL.
- Use `Ctrl+P` / `Cmd+P` in Obsidian → run “Slurp: save URL” command.
- Paste URL, hit enter, and Obsidian opens the newly created article note ready for reading, highlighting, or linking.
- Slurp currently accelerates capture via a bookmarklet:
- Create a new bookmark; paste Slurp’s provided JavaScript into the URL field.
- Clicking this bookmarklet from any article page triggers Slurp’s save flow to Obsidian.
- With Vimium C or similar keyboard tools, you can trigger the bookmarklet with keystrokes, though browsers may still require a click to confirm running JavaScript.
- Browser extensions are under development; once available, they are expected to streamline capture further and hopefully enable near-full keyboard control.
- In practice, Slurp has replaced both Obsidian Web Clipper and ReadItLater in the author’s workflow; those plugins have been fully disabled.
## 📚 References
- Slurp plugin (GitHub) — linked from the article’s description on the site.
- Obsidian: https://obsidian.md/
- Vimium C: https://github.com/gdh1995/vimium-c
## 🗣️ Paraphrase
- Paragraph A paraphrase.
- The author describes frustration with existing Obsidian clipping tools that required multiple steps and often failed, then explains that finding Slurp in the plugin directory immediately resolved these issues.
- Paragraph B paraphrase.
- They outline how to configure Slurp’s settings (folder, properties, tags) and use Obsidian’s command palette to save URLs, plus how a bookmarklet and future browser extensions make the capture process faster and smoother.
## 📰 Newsletter
Struggling to get web articles cleanly into Obsidian? Curtis McHale just shared how the Slurp plugin replaced both ReadItLater and Obsidian Web Clipper in his workflow. With a quick folder configuration and a simple “paste URL” command, Slurp drops full pages straight into your vault—no double-saving, no flakiness. There’s even a bookmarklet today and browser extensions on the way, making it a strong option for WordPress builders who rely on Obsidian for research, docs, and content planning.
## ✅ Action Items
#### DevRel
- Document a “research-to-Obsidian” workflow using Slurp for developer guides and samples.
- Record a short demo video showing Slurp capturing API docs, changelogs, or tutorial pages.
- Add Slurp-based examples to quickstart templates for engineering blogs and docs stacks.
- Track click-through and adoption from blog posts or docs pages that recommend Slurp.
- Encourage community feedback on edge cases (auth-required pages, heavy JS sites).
#### OSPO
- Clarify any license and security review requirements for using third-party Obsidian plugins in enterprise environments.
- Add Slurp (or similar tooling) to recommended workflows for engineers keeping internal knowledge bases.
- Ensure documentation explains data paths and privacy (local vs. remote storage).
#### Community
- Host a short session or livestream on “PKM workflows for developers” featuring Slurp.
- Maintain a community-curated list of reliable Obsidian capture plugins and recipes.
- Encourage contributors to share vault folder structures and property presets for Slurp.
#### WordPress
- Core: Document how contributors can clip Trac tickets, dev notes, and proposals into Obsidian via Slurp.
- Core Performance: Capture profiling reports and benchmark posts into a shared Obsidian vault.
- Core AI: Save AI-related RFCs and experiments with consistent metadata fields in Slurp templates.
- **Core Program Team:** Standardize note templates for project updates captured from Make blogs.
- Mobile: Use Slurp to archive platform-specific docs and store repeatable debugging checklists.
- Playground: Clip Playground recipes and bug repro steps from forum threads into Obsidian.
- Community: Provide a “PKM for organizers” guide using Slurp for meetup and WordCamp logistics notes.
- Training: Build lesson plans in Obsidian sourced from tutorials and documentation captured via Slurp.
- Marketing: Funnel campaign briefs and competitor research into a shared Obsidian workspace.
- Support: Capture high-signal support threads and canonical answers to feed into docs and FAQs.
- Design: Keep design references and patterns clipped from across the web in a design vault.
- Documentation: Maintain a vault for doc style guides, examples, and external sources, filled via Slurp.
- Photos: Use Slurp to capture licensing and usage guidelines from external media sites.
- TV: Archive talk descriptions, outlines, and external references into a speaker-prep vault.
- Polyglots: Clip localization guidance and language references into language-team notes.
- Accessibility: Capture WCAG references and audit writeups; tag by criterion.
- Meta: Save .org infrastructure docs and hosting policies from external sources.
- CLI: Keep command usage patterns and blog examples accessible in a CLI-focused vault.
- Hosting: Capture best-practice posts from hosting blogs for cross-host standards.
- Tide: Clip scoring, quality, and security references to inform scoring models.
- Openverse: Store policy and moderation references for media reuse.
- Themes: Collect design system articles and theme best practices.
- Plugins: Archive plugin security and architecture references for reviewers.
#### The WPOCC
- Programs: Prototype a “PKM for maintainers” track featuring Obsidian + Slurp workflows.
- Projects: Run documentation sprints where research is captured via Slurp into shared vaults.
- Funding experiments: Log grant proposals and reporting templates into Obsidian for reuse.
### FAIR
- Technical independence: Encourage local-first note-taking (Obsidian) and clarify Slurp’s local-only behavior.
- Policies and covenants: Document any plugin selection criteria and security expectations in Obsidian.
- Productized governance artifacts: Store governance templates and scorecards in a vault seeded with captured examples.
## 🧪 Hypotheses
- H1: Obsidian users with Slurp-enabled capture will save more web articles per week than those using traditional web clippers.
- H2: A single, reliable capture plugin reduces friction enough to increase actual review/annotation of saved articles.
- H3: Browser extensions for Slurp will cut average “time to captured note” by at least 30% compared to the bookmarklet workflow.
### 📊 Methodology
- Compare capture logs (or note metadata) before and after adopting Slurp for a group of users.
- Survey users on perceived friction, failure rates, and annotation frequency.
- Time the capture flow (from “decide to save” to “note open in Obsidian”) across different tools and setups.
### ❓ Questions
- How well does Slurp handle complex, JS-heavy pages or paywalled content?
- What are Slurp’s failure modes, and how does it inform the user when capture fails?
- Can Slurp standardize metadata across multiple teams sharing a vault?
### 🔮 Future Research
- Evaluate Slurp vs. other Obsidian clipping plugins across a broad range of websites.
- Explore integrating Slurp with read-it-later services (e.g., Omnivore, Reader) or RSS.
- Investigate templates and automation (e.g., Templater, Dataview) powered by Slurp-captured notes.
### 💡 Implications
- Practice: Better capture fosters consistent reading and synthesis habits inside Obsidian.
- Policy: Teams may formalize “how to save research” guidelines around a single tool like Slurp.
- Security: Local-first capture reduces exposure compared to cloud-based clipping options.
- Education: Instructors can build repeatable research workflows for students using Obsidian + Slurp.
- Funding models: Maintainers of high-leverage PKM plugins like Slurp may warrant financial support.
### 🧠 Learning Styles Assessment
- Reading level estimate: ~8th–9th grade (Flesch-Kincaid style; short sentences, minimal jargon).
#### 👀 Visual learners
- Present: Screenshot mentions (settings, dialogs) in the article.
- Improve: Add actual annotated screenshots and a simple flow diagram of the capture process.
#### 🔊 Aural learners
- Present: None explicitly.
- Improve: Short audio walkthrough or screencast narrating the Slurp setup and capture flow.
#### 🗣️ Verbal learners
- Present: Clear step-by-step explanations in plain language.
- Improve: Add analogies comparing Slurp to familiar tools like browser “share” menus or Pocket.
#### 🧩 Kinesthetic learners
- Present: Concrete steps for configuring Slurp and setting up a bookmarklet.
- Improve: Include a checklist and a small “practice run” exercise capturing 3–5 articles.
#### 🧠 Logical learners
- Present: Sequential process descriptions and cause-effect (“old tools failed, Slurp fixes this”).
- Improve: Add a pros/cons table comparing capture plugins and workflows.
#### 🧑🤝🧑 Social learners
- Present: Implicitly, a plugin used by the Obsidian community.
- Improve: Link to community threads, examples, and shared vault structures using Slurp.
#### 🧘♀️ Solitary learners
- Present: Quiet, self-paced instructions and a simple narrative.
- Improve: Reflection prompts on designing a personal vault structure for captured web content.
#### 🌿 Naturalistic learners
- Present: No explicit nature framing.
- Improve: Use analogies (e.g., “gardening your web captures”) or tie to sustainable digital organization.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Likely basic headings and images with captions (depending on site theme).
- Improve: Ensure descriptive alt text for screenshots and clear heading hierarchy.
#### Keyboard navigation
- Present: Standard WordPress navigation (theme-dependent).
- Improve: Verify focus states, skip links, and no keyboard traps around embedded media.
#### Contrast and readability
- Present: Typical blog contrast and font sizing.
- Improve: Confirm 4.5:1 contrast ratio and adequate line height on all devices.
#### Text resizing and reflow
- Present: Responsive layout via WordPress theme.
- Improve: Test at 200% zoom and with reduced-motion preferences.
#### Media and captions
- Present: Screenshots only, no audio/video.
- Improve: If screencasts are added, provide captions and transcripts.
#### Forms and interactions
- Present: None within the article body.
- Improve: N/A beyond general site contact/comment forms.
#### Standards reference
- Map gaps to WCAG 2.2 AA for non-text contrast, reflow, focus visible, and consistent navigation.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: General technical content, culturally neutral.
- Improve: Include examples from varied user contexts (students, NGOs, different regions).
#### Inclusive language
- Present: Neutral, non-gendered wording; minimal jargon.
- Improve: Add short definitions for terms like “bookmarklet” and “Vimium C.”
#### Neurodiversity support
- Present: Short sections, clear steps.
- Improve: More headings, bullet lists, and consistent visual patterns for instructions.
#### Representation
- Present: No explicit people imagery; neutral.
- Improve: If images are added, ensure inclusive representation in visuals and alt text.
#### Psychological safety
- Present: Calm, problem-solving tone, no shaming of prior tools or users.
- Improve: Add explicit encouragement to experiment and adapt workflows without “right/wrong” framing.
### ✅ Logical Validity
#### Strong reasoning
- The article uses practical causal reasoning: previous tools caused repeated failures; a new plugin removed those failures, so the workflow improved. This is clear, experience-based, and easy to verify.
#### Fallacies
- None obvious; it does not claim Slurp is universally superior, only that it solved the author’s problems.
#### Tone of voice
- Pragmatic, solution-focused, and mildly tutorial: identifies a pain point, then walks through the fix without hype.
### 🛡️ DARVO Analysis
- Deny: No denial or minimization of problems; the failures of prior tools are openly acknowledged.
- Attack: No attacks on tool authors or users.
- Reverse victim/offender: Not present; the article simply states that the author experienced issues and found a better option.
## 🎯 Conclusion
Slurp provides a straightforward, reliable path to capture web articles into Obsidian, replacing older, brittle solutions in the author’s stack. With simple configuration, a command-palette flow, and a bookmarklet (plus future extensions), it meaningfully lowers friction for research and reading workflows. Next steps for readers: install Slurp, set a dedicated capture folder, test the bookmarklet, and iterate on properties and templates that fit their vault.
## 🧱 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] 5–10-word present-tense claim
> [!quote] [Slurp Fixed Saving Web Articles to Obsidian](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/) by [[Curtis McHale]] via [[curtismchale.ca]]. Published 2026-01-08.
> “A day after that video I was annoyed and searched ‘Read Later’ in the community plugin manager and then found Slurp.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [Slurp Fixed Saving Web Articles to Obsidian](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/)
> “So, Slurp solves the issues I had with Obsidian Web Clipper and the ReadItLater plugin and I’ve turned them off.”
Two lines: context and use.
[view highlight](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/#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] Slurp replaces unreliable Obsidian clippers
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Obsidian-Workflows]] [[Web-Capture]]
#### [Z2] Bookmarklets accelerate Obsidian web capture
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Browser-Automation]] [[Obsidian-Web-Clipper]]
---
### ✏️ 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] Try Slurp as primary Obsidian web capture tool — context/https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/ #fleeting #inbox
- [F2] Design a standard web-article template for Slurp captures — context/https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/ #fleeting #inbox
- [F3] Test Slurp bookmarklet vs. future browser extensions — context/https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/ #fleeting #inbox
---
<!-- deep-read:sections end -->
[[3. Resources/Readwise/Full Document Contents/Articles/Slurp Fixed Saving Web Articles to Obsidian|Full Document Contents]]
## Document Notes
```markdown
---
tags: #obsidian #plugins #read-it-later
author: Curtis McHale
source: curtismchale.ca
reference: [https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/]
date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
---
# 🏷️ Title: Slurp Fixed Saving Web Articles to Obsidian
## 🧭 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
- What happened.
- The author replaced broken Obsidian capture tools (ReadItLater, Obsidian Web Clipper) with the Slurp plugin to save web articles reliably.
- Why it matters.
- Stable capture is foundational for any Obsidian-based reading, research, or PKM workflow.
- Key stakeholders.
- Obsidian users, plugin maintainers, knowledge workers who save web content.
- Risks and tradeoffs.
- Depends on a single community plugin; browser extensions are still in progress; bookmarklet requires some manual interaction.
- Bottom line.
- Slurp provides a simpler, more reliable “save to Obsidian” flow today, with a likely better UX once official browser extensions land.
## 📖 Main Content
- Explain the core arguments in plain language.
- Previously, saving web pages into Obsidian required two tools that were unreliable. The author searched the community plugins for “Read Later,” found Slurp, and discovered it solved the capture issues on the first try.
- Slurp lets you configure where notes land (e.g., `Sources/Clippings`) and how properties and tags are handled, then save any page by copying its URL, running the Slurp command from Obsidian’s command palette, pasting the link, and jumping directly to the new note.
- For faster capture, Slurp offers a JavaScript bookmarklet today and is developing full browser extensions, which should reduce friction further.
- Add sourced context and define terms.
- Obsidian is a local-first Markdown note app; its ecosystem depends heavily on plugins to extend core behavior, including web clipping.
- A bookmarklet is a browser bookmark whose “URL” is JavaScript; it runs in-page to perform an action, here triggering Slurp via Obsidian.
- Note uncertainties or contested claims.
- The article reports personal experience, not benchmarks across many sites or edge cases.
- Stability over time depends on Slurp’s maintenance and Obsidian/plugin API changes.
### 🗒️ Notes
- The author’s previous stack (ReadItLater + Obsidian Web Clipper) required saving pages twice and still didn’t consistently capture the desired content.
- A search for “Read Later” in Obsidian’s community plugin manager surfaced Slurp, which immediately fixed the reliability problem for the author.
- Key configuration: setting the destination folder (e.g., `Sources/Clippings`) to integrate with an existing vault structure; optional tweaks include property ordering and tag parsing.
- The author prefers “Tag Notes” over inline tags, so Slurp’s tag-based features are left off, signaling that Slurp works even in tag-minimal workflows.
- Capture flow:
- Navigate to a target web page.
- Copy the URL.
- Use `Ctrl+P` / `Cmd+P` in Obsidian → run “Slurp: save URL” command.
- Paste URL, hit enter, and Obsidian opens the newly created article note ready for reading, highlighting, or linking.
- Slurp currently accelerates capture via a bookmarklet:
- Create a new bookmark; paste Slurp’s provided JavaScript into the URL field.
- Clicking this bookmarklet from any article page triggers Slurp’s save flow to Obsidian.
- With Vimium C or similar keyboard tools, you can trigger the bookmarklet with keystrokes, though browsers may still require a click to confirm running JavaScript.
- Browser extensions are under development; once available, they are expected to streamline capture further and hopefully enable near-full keyboard control.
- In practice, Slurp has replaced both Obsidian Web Clipper and ReadItLater in the author’s workflow; those plugins have been fully disabled.
## 📚 References
- Slurp plugin (GitHub) — linked from the article’s description on the site.
- Obsidian: https://obsidian.md/
- Vimium C: https://github.com/gdh1995/vimium-c
## 🗣️ Paraphrase
- Paragraph A paraphrase.
- The author describes frustration with existing Obsidian clipping tools that required multiple steps and often failed, then explains that finding Slurp in the plugin directory immediately resolved these issues.
- Paragraph B paraphrase.
- They outline how to configure Slurp’s settings (folder, properties, tags) and use Obsidian’s command palette to save URLs, plus how a bookmarklet and future browser extensions make the capture process faster and smoother.
## 📰 Newsletter
Struggling to get web articles cleanly into Obsidian? Curtis McHale just shared how the Slurp plugin replaced both ReadItLater and Obsidian Web Clipper in his workflow. With a quick folder configuration and a simple “paste URL” command, Slurp drops full pages straight into your vault—no double-saving, no flakiness. There’s even a bookmarklet today and browser extensions on the way, making it a strong option for WordPress builders who rely on Obsidian for research, docs, and content planning.
## ✅ Action Items
#### DevRel
- Document a “research-to-Obsidian” workflow using Slurp for developer guides and samples.
- Record a short demo video showing Slurp capturing API docs, changelogs, or tutorial pages.
- Add Slurp-based examples to quickstart templates for engineering blogs and docs stacks.
- Track click-through and adoption from blog posts or docs pages that recommend Slurp.
- Encourage community feedback on edge cases (auth-required pages, heavy JS sites).
#### OSPO
- Clarify any license and security review requirements for using third-party Obsidian plugins in enterprise environments.
- Add Slurp (or similar tooling) to recommended workflows for engineers keeping internal knowledge bases.
- Ensure documentation explains data paths and privacy (local vs. remote storage).
#### Community
- Host a short session or livestream on “PKM workflows for developers” featuring Slurp.
- Maintain a community-curated list of reliable Obsidian capture plugins and recipes.
- Encourage contributors to share vault folder structures and property presets for Slurp.
#### WordPress
- Core: Document how contributors can clip Trac tickets, dev notes, and proposals into Obsidian via Slurp.
- Core Performance: Capture profiling reports and benchmark posts into a shared Obsidian vault.
- Core AI: Save AI-related RFCs and experiments with consistent metadata fields in Slurp templates.
- **Core Program Team:** Standardize note templates for project updates captured from Make blogs.
- Mobile: Use Slurp to archive platform-specific docs and store repeatable debugging checklists.
- Playground: Clip Playground recipes and bug repro steps from forum threads into Obsidian.
- Community: Provide a “PKM for organizers” guide using Slurp for meetup and WordCamp logistics notes.
- Training: Build lesson plans in Obsidian sourced from tutorials and documentation captured via Slurp.
- Marketing: Funnel campaign briefs and competitor research into a shared Obsidian workspace.
- Support: Capture high-signal support threads and canonical answers to feed into docs and FAQs.
- Design: Keep design references and patterns clipped from across the web in a design vault.
- Documentation: Maintain a vault for doc style guides, examples, and external sources, filled via Slurp.
- Photos: Use Slurp to capture licensing and usage guidelines from external media sites.
- TV: Archive talk descriptions, outlines, and external references into a speaker-prep vault.
- Polyglots: Clip localization guidance and language references into language-team notes.
- Accessibility: Capture WCAG references and audit writeups; tag by criterion.
- Meta: Save .org infrastructure docs and hosting policies from external sources.
- CLI: Keep command usage patterns and blog examples accessible in a CLI-focused vault.
- Hosting: Capture best-practice posts from hosting blogs for cross-host standards.
- Tide: Clip scoring, quality, and security references to inform scoring models.
- Openverse: Store policy and moderation references for media reuse.
- Themes: Collect design system articles and theme best practices.
- Plugins: Archive plugin security and architecture references for reviewers.
#### The WPCC
- Programs: Prototype a “PKM for maintainers” track featuring Obsidian + Slurp workflows.
- Projects: Run documentation sprints where research is captured via Slurp into shared vaults.
- Funding experiments: Log grant proposals and reporting templates into Obsidian for reuse.
### FAIR
- Technical independence: Encourage local-first note-taking (Obsidian) and clarify Slurp’s local-only behavior.
- Policies and covenants: Document any plugin selection criteria and security expectations in Obsidian.
- Productized governance artifacts: Store governance templates and scorecards in a vault seeded with captured examples.
## 🧪 Hypotheses
- H1: Obsidian users with Slurp-enabled capture will save more web articles per week than those using traditional web clippers.
- H2: A single, reliable capture plugin reduces friction enough to increase actual review/annotation of saved articles.
- H3: Browser extensions for Slurp will cut average “time to captured note” by at least 30% compared to the bookmarklet workflow.
### 📊 Methodology
- Compare capture logs (or note metadata) before and after adopting Slurp for a group of users.
- Survey users on perceived friction, failure rates, and annotation frequency.
- Time the capture flow (from “decide to save” to “note open in Obsidian”) across different tools and setups.
### ❓ Questions
- How well does Slurp handle complex, JS-heavy pages or paywalled content?
- What are Slurp’s failure modes, and how does it inform the user when capture fails?
- Can Slurp standardize metadata across multiple teams sharing a vault?
### 🔮 Future Research
- Evaluate Slurp vs. other Obsidian clipping plugins across a broad range of websites.
- Explore integrating Slurp with read-it-later services (e.g., Omnivore, Reader) or RSS.
- Investigate templates and automation (e.g., Templater, Dataview) powered by Slurp-captured notes.
### 💡 Implications
- Practice: Better capture fosters consistent reading and synthesis habits inside Obsidian.
- Policy: Teams may formalize “how to save research” guidelines around a single tool like Slurp.
- Security: Local-first capture reduces exposure compared to cloud-based clipping options.
- Education: Instructors can build repeatable research workflows for students using Obsidian + Slurp.
- Funding models: Maintainers of high-leverage PKM plugins like Slurp may warrant financial support.
### 🧠 Learning Styles Assessment
- Reading level estimate: ~8th–9th grade (Flesch-Kincaid style; short sentences, minimal jargon).
#### 👀 Visual learners
- Present: Screenshot mentions (settings, dialogs) in the article.
- Improve: Add actual annotated screenshots and a simple flow diagram of the capture process.
#### 🔊 Aural learners
- Present: None explicitly.
- Improve: Short audio walkthrough or screencast narrating the Slurp setup and capture flow.
#### 🗣️ Verbal learners
- Present: Clear step-by-step explanations in plain language.
- Improve: Add analogies comparing Slurp to familiar tools like browser “share” menus or Pocket.
#### 🧩 Kinesthetic learners
- Present: Concrete steps for configuring Slurp and setting up a bookmarklet.
- Improve: Include a checklist and a small “practice run” exercise capturing 3–5 articles.
#### 🧠 Logical learners
- Present: Sequential process descriptions and cause-effect (“old tools failed, Slurp fixes this”).
- Improve: Add a pros/cons table comparing capture plugins and workflows.
#### 🧑🤝🧑 Social learners
- Present: Implicitly, a plugin used by the Obsidian community.
- Improve: Link to community threads, examples, and shared vault structures using Slurp.
#### 🧘♀️ Solitary learners
- Present: Quiet, self-paced instructions and a simple narrative.
- Improve: Reflection prompts on designing a personal vault structure for captured web content.
#### 🌿 Naturalistic learners
- Present: No explicit nature framing.
- Improve: Use analogies (e.g., “gardening your web captures”) or tie to sustainable digital organization.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Likely basic headings and images with captions (depending on site theme).
- Improve: Ensure descriptive alt text for screenshots and clear heading hierarchy.
#### Keyboard navigation
- Present: Standard WordPress navigation (theme-dependent).
- Improve: Verify focus states, skip links, and no keyboard traps around embedded media.
#### Contrast and readability
- Present: Typical blog contrast and font sizing.
- Improve: Confirm 4.5:1 contrast ratio and adequate line height on all devices.
#### Text resizing and reflow
- Present: Responsive layout via WordPress theme.
- Improve: Test at 200% zoom and with reduced-motion preferences.
#### Media and captions
- Present: Screenshots only, no audio/video.
- Improve: If screencasts are added, provide captions and transcripts.
#### Forms and interactions
- Present: None within the article body.
- Improve: N/A beyond general site contact/comment forms.
#### Standards reference
- Map gaps to WCAG 2.2 AA for non-text contrast, reflow, focus visible, and consistent navigation.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: General technical content, culturally neutral.
- Improve: Include examples from varied user contexts (students, NGOs, different regions).
#### Inclusive language
- Present: Neutral, non-gendered wording; minimal jargon.
- Improve: Add short definitions for terms like “bookmarklet” and “Vimium C.”
#### Neurodiversity support
- Present: Short sections, clear steps.
- Improve: More headings, bullet lists, and consistent visual patterns for instructions.
#### Representation
- Present: No explicit people imagery; neutral.
- Improve: If images are added, ensure inclusive representation in visuals and alt text.
#### Psychological safety
- Present: Calm, problem-solving tone, no shaming of prior tools or users.
- Improve: Add explicit encouragement to experiment and adapt workflows without “right/wrong” framing.
### ✅ Logical Validity
#### Strong reasoning
- The article uses practical causal reasoning: previous tools caused repeated failures; a new plugin removed those failures, so the workflow improved. This is clear, experience-based, and easy to verify.
#### Fallacies
- None obvious; it does not claim Slurp is universally superior, only that it solved the author’s problems.
#### Tone of voice
- Pragmatic, solution-focused, and mildly tutorial: identifies a pain point, then walks through the fix without hype.
### 🛡️ DARVO Analysis
- Deny: No denial or minimization of problems; the failures of prior tools are openly acknowledged.
- Attack: No attacks on tool authors or users.
- Reverse victim/offender: Not present; the article simply states that the author experienced issues and found a better option.
## 🎯 Conclusion
Slurp provides a straightforward, reliable path to capture web articles into Obsidian, replacing older, brittle solutions in the author’s stack. With simple configuration, a command-palette flow, and a bookmarklet (plus future extensions), it meaningfully lowers friction for research and reading workflows. Next steps for readers: install Slurp, set a dedicated capture folder, test the bookmarklet, and iterate on properties and templates that fit their vault.
## 🧱 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] 5–10-word present-tense claim
> [!quote] [Slurp Fixed Saving Web Articles to Obsidian](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/) by [[Curtis McHale]] via [[curtismchale.ca]]. Published 2026-01-08.
> “A day after that video I was annoyed and searched ‘Read Later’ in the community plugin manager and then found Slurp.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [Slurp Fixed Saving Web Articles to Obsidian](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/)
> “So, Slurp solves the issues I had with Obsidian Web Clipper and the ReadItLater plugin and I’ve turned them off.”
Two lines: context and use.
[view highlight](https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/#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] Slurp replaces unreliable Obsidian clippers
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Obsidian-Workflows]] [[Web-Capture]]
#### [Z2] Bookmarklets accelerate Obsidian web capture
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Browser-Automation]] [[Obsidian-Web-Clipper]]
---
### ✏️ 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] Try Slurp as primary Obsidian web capture tool — context/https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/ #fleeting #inbox
- [F2] Design a standard web-article template for Slurp captures — context/https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/ #fleeting #inbox
- [F3] Test Slurp bookmarklet vs. future browser extensions — context/https://curtismchale.ca/2026/01/08/slurp-fixed-saving-web-articles-to-obsidian/ #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.
[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: 0 • #xref: 0 • #share: 0 • #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
- After that, head to a web page you want to save, copy the url and then you can use `CTRL P` (`CMD P` on macOS) to bring up the command palette. Type `Slurp` and then press enter on the action that saves a url. This brings up a dialogue where you paste your url in, then press enter. ([View Highlight](https://read.readwise.io/read/01keht6c555ar1gk3rnexzhpve))
- Tags: 👻 ai highlighted