Fix clipper post typo, bad link

pages/20241129-obsidian-webclipper-config/index.md

@@ -3,18 +3,20 @@ date: 2024-11-29
 title: Create Obsidian Web Clip Summaries on MacOS with Firefox and Llama 3.2
 excerpt: I use Obsidian to capture all kinds of information. I set out to get the Obsidian web clipper Firefox extension configured on my Mac with a local Meta Llama 3.2 model to summarize content. This post explains the steps I took top-to-bottom.
 ---
+
 I use [Obsidian](https://obsidian.md) to capture information like my daily todo lists; notes about things I've read, listened to, watched, or done; reminders about repeating chores and home maintenance tasks; trips I'm planning or places I've visited--anything and everything.
 
 I recently learned about the [Obsidian web clipper](https://github.com/obsidianmd/obsidian-clipper) browser extension. I was intrigued by some of the features [shown on the landing page](https://obsidian.md/clipper). I started thinking about how it might improve my workflows for indexing web pages that I want to go back and read in more detail and distilling them into notes for quick reference later. Instead of manually entering all of the page metadata, copy/pasting text from the page into a note, and writing a quick summary, maybe the extension could take a first pass for me.
 
 I set out to get the [web clipper Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/web-clipper-obsidian/) configured on my Mac, with a local [Meta Llama 3.2](https://ollama.com/library/llama3.2) model set as an [interpreter](https://help.obsidian.md/web-clipper/interpreter) to summarize content in some of my [templates](https://help.obsidian.md/web-clipper/templates). The [Obsidian help pages](https://help.obsidian.md/web-clipper) explained the basics. I wrote this post to describe the steps I took from top-to-bottom, including what I did to get summaries of acceptable quality in my clippings.[^1]
+
 # Prereqs
 
 I started with the following:
 
 - Macbook Pro M2 w/ 16 GB RAM
 - macOS Sequoia 15.x
-- [homebrew](https://homebrew.sh)
+- [homebrew](https://brew.sh)
 - [Firefox](https://www.mozilla.org/en-US/firefox/) (`brew install --cask firefox`)
 - [Obsidian](https://obsidian.md) >=1.7.2 (`brew install --cask obsidian`)
 
@@ -37,12 +39,14 @@ At this point, I was able to open the extension, click the highlighter icon, sel
 # Page Summaries
 
 I created a second template that includes a generated page summary in addition to my highlights by taking these steps.
+
 ## Create an ollama model for summarization
 
-1. Install the Ollama macOS  desktop app and CLI with `brew install --cask ollama`.
+1. Install the Ollama macOS desktop app and CLI with `brew install --cask ollama`.
 2. Run `launchctl setenv OLLAMA_ORIGINS 'moz-extension://*'` so that the local Ollama server will accept connections from my Firefox browser.[^2]
 3. Run the Ollama macOS app from the finder and work through the setup dialog screens until they disappear.[^3]
 4. Create a `Modelfile` with the following content.
+
 ```
 # Use the 3B parameter, 2 GB base model file
 FROM llama3.2
@@ -51,6 +55,7 @@ PARAMETER num_ctx 32768
 # Lower temperature for more conservative sampling / less creative summaries
 PARAMETER temperature 0.25
 ```
+
 5. Run `ollama create -f Modelfile llama3.2:ctx32k-t0.25` to create a model config with that ID.
 6. Run `ollama list` and confirm the base and custom models exist.
 
@@ -59,11 +64,11 @@ PARAMETER temperature 0.25
 1. Click the Obsidian icon in the Firefox toolbar and then click the gear to open the settings screen again.
 2. Click _Interpreter_ and enable it.
 3. Click _Add model_ and enter details about the local Ollama server.
-	- _Display name_: `Llama 3.2 (ctx=32k, t=0.25)`
-	- _Base URL_: `http://127.0.0.1:11434/api/chat`
-	- _Model ID_: `llama3.2:ctx32k-t0.25` (the ID used when running `ollama create` earlier)
-	- _Provider_: `Ollama`
-	- _API key_: `ollama`
+   - _Display name_: `Llama 3.2 (ctx=32k, t=0.25)`
+   - _Base URL_: `http://127.0.0.1:11434/api/chat`
+   - _Model ID_: `llama3.2:ctx32k-t0.25` (the ID used when running `ollama create` earlier)
+   - _Provider_: `Ollama`
+   - _API key_: `ollama`
 4. Drag the new model so that it appears first and disable the other models.
 
 ## Create a new template
@@ -72,6 +77,7 @@ PARAMETER temperature 0.25
 2. Click _More -> Duplicate_ at the top.
 3. Name the new template _Summary and Highlights_.
 4. Update the _Note content_ to include a prompt variable.
+
 ```markdown
 # AI Summary
 
@@ -81,7 +87,9 @@ PARAMETER temperature 0.25
 
 {{highlights|map: item => item.text|join:"\n\n"}}
 ```
+
 5. Update the _Interpreter context_ to include a slice of the page content smaller than the context window configured for the model.
+
 ```markdown
 <documentPrefix>{{content|slice:0,16384}}</documentPrefix>
 ```
@@ -100,6 +108,7 @@ I found that my generic _Summary and Highlights_ template did not work on all si
 4. Name the new template _AWS Docs Summary and Highlights_.
 5. Put `https://docs.aws.amazon.com/` in the _Template triggers_ textbox.
 6. Update the _Note content_ with a slightly customized prompt.
+
 ```markdown
 # AI Summary
 
@@ -109,14 +118,17 @@ I found that my generic _Summary and Highlights_ template did not work on all si
 
 {{highlights|map: item => item.text|join:"\n\n"}}
 ```
+
 7. Update the _Interpreter context_ to pull content from the HTML element with `id="main"` instead of [where the extension gets it by default](https://help.obsidian.md/web-clipper/troubleshoot#Some+content+is+missing).
+
 ```markdown
 <documentPrefix>{{selectorHtml:#main|markdown|slice:0,16384}}</documentPrefix>
 ```
 
- I was able to visit one of the [Amazon Bedrock documentation pages](https://docs.aws.amazon.com/bedrock/latest/userguide/tool-use-inference-call.html) and generate a meaningful summary after configuring this template for automatic activation on the https://docs.aws.amazon.com site.
+I was able to visit one of the [Amazon Bedrock documentation pages](https://docs.aws.amazon.com/bedrock/latest/userguide/tool-use-inference-call.html) and generate a meaningful summary after configuring this template for automatic activation on the https://docs.aws.amazon.com site.
 
 ![Screenshot of the web clipper automatically switching to the AWS Docs Summary and Highlights template and generating a custom summary when visiting an AWS documentation page](./clip-aws-docs.png)
+
 # Final Thoughts
 
 - The web clipper extension is in beta as of this writing. I expect the UX will change.
@@ -125,4 +137,4 @@ I found that my generic _Summary and Highlights_ template did not work on all si
 
 [^1]: I'm maintaining my latest Obsidian configs in [parente/obsidian-configs on GitHub](https://github.com/parente/obsidian-configs).
 [^2]: I did spend a few moments considering if I should set this env var less globally and narrow down the extension UUID(s) allowed. I did not think it worth the effort in my case. Follow your heart.
-[^3]: Restart the Ollama app from the macOS menu bar if you're already running it so that the `launchtl setenv` takes effect. Otherwise, the ollama server will respond with auth errors when the extension attempts to use it.
+[^3]: Restart the Ollama app from the macOS menu bar if you're already running it so that the `launchctl setenv` takes effect. Otherwise, the ollama server will respond with auth errors when the extension attempts to use it.