First init.

3. Resources/Knowledgebase/Troubleshooting Trees/Untitled.md

@@ -0,0 +1,72 @@
+# 📦 Barcode Printing Issues — Troubleshooting Tree
+
+## Step 1: Identify the Printing Path
+- [ ] Is the label supposed to print **directly from Epicor (SSRS/Edge Agent)**? → Go to **Path A**
+- [ ] Or is it sent to **Azure share → Bartender Integration Service**? → Go to **Path B**
+
+---
+
+## 🔹 Path A — Epicor (SSRS → Edge Agent → Printer)
+
+### Step 2A: Did the SSRS report generate correctly in Epicor?
+- [ ] Yes → Go to Step 3A
+- [ ] No → Check report parameters, dataset, or permissions in Epicor
+
+### Step 3A: Did the Edge Agent receive the print job?
+- [ ] Yes → Go to Step 4A
+- [ ] No → Check Edge Agent service status on the client/server
+  - Restart Edge Agent service if stopped
+  - Review logs in `C:\ProgramData\Epicor Software Corporation\EdgeAgent\Logs`
+
+### Step 4A: Was the job sent to the correct printer?
+- [ ] Yes → Go to Step 5A
+- [ ] No → Verify printer mapping in Epicor → Company/Plant/Workstation settings
+
+### Step 5A: Is the printer online and reachable?
+- [ ] Yes → Check Windows print queue for stuck jobs
+- [ ] No → Power cycle printer, verify network connectivity, driver status
+
+---
+
+## 🔹 Path B — Azure Share → Bartender Integration Service → Printer
+
+### Step 2B: Did Epicor export the file to the Azure share?
+- [ ] Yes → Go to Step 3B
+- [ ] No → Verify Epicor report style is set to **Export**, confirm user has write access to share
+
+### Step 3B: Did the file appear in the watched folder?
+- [ ] Yes → Go to Step 4B
+- [ ] No → Check Azure storage permissions, sync status, or network connectivity
+
+### Step 4B: Did the Bartender Integration Service pick up the file?
+- [ ] Yes → Go to Step 5B
+- [ ] No →
+  - Check Bartender Integration logs in `C:\ProgramData\Seagull\Bartender\Logs`
+  - Confirm the integration service is running
+  - Validate file naming convention matches trigger rules
+
+### Step 5B: Was the file processed into a print job?
+- [ ] Yes → Go to Step 6B
+- [ ] No → Check Bartender template config, action rules, and variables
+
+### Step 6B: Was the job sent to the correct printer?
+- [ ] Yes → Go to Step 7B
+- [ ] No → Confirm Bartender printer mapping settings
+
+### Step 7B: Is the printer online and reachable?
+- [ ] Yes → Check Windows print queue for stuck jobs
+- [ ] No → Power cycle printer, verify network connectivity, driver status
+
+---
+
+## 🚩 Escalation Points
+- **SSRS failures** → ERP/report developer
+- **Edge Agent service errors** → Epicor admin / IT infra
+- **Bartender misconfigurations** → automation admin / IT infra
+- **Persistent printer errors** → local IT / vendor support
+
+---
+
+## 🧭 Notes
+- Keep a **sample successful job log** for both Epicor and Bartender as a baseline.
+- Document **which printers use which path** (Edge Agent vs Bartender).

3. Resources/Obsidian/Admonition Plugin Cheat Sheet.md

@@ -0,0 +1,112 @@
+## Basic syntax
+
+Admonitions use *fenced code blocks* whose language is `ad-<type>`.  
+Everything inside is the content of the admonition.  
+
+```ad-note
+title: Optional Title Here
+collapse: open|close|none   ← (optional) how it starts
+This is the body content of your admonition.
+You can write Markdown inside.
+```
+
+- The `title:` field is optional. If omitted, it uses the default title for that type (e.g. “Note” for `ad-note`). :contentReference[oaicite:0]{index=0}  
+- The `collapse:` field controls whether the admonition starts open or closed. Options: `open`, `close`, or `none` (no collapsing). :contentReference[oaicite:1]{index=1}  
+
+---
+
+## ✅ Default types
+
+Here are some of the built-in types (i.e. the `type` part after `ad-`) that you’ll commonly use (with default behaviors/icons):
+
+- ad-note  
+- ad-info  
+- ad-tip  
+- ad-warning  
+- ad-caution / ad-attention  
+- ad-danger / ad-error  
+- ad-success  
+- ad-example  
+- ad-question / ad-help  
+- ad-abstract / ad-summary / ad-tldr  
+- ad-failure / ad-fail / ad-missing  
+- ad-bug  
+
+(Yes, there are synonyms and variants. The settings allow some custom types. ) :contentReference[oaicite:2]{index=2}
+
+---
+
+## 🔄 Nested admonitions
+
+You can put admonitions *inside* other admonitions. This is great for making structured content like troubleshooting trees. Nested blocks must still follow the fenced code block + `ad-type` syntax. :contentReference[oaicite:3]{index=3}
+
+Example:
+
+```ad-note
+title: Parent Note
+collapse: open
+
+This is the parent admonition content.
+
+```ad-warning
+title: Nested Warning
+collapse: close
+This is a warning inside the note.
+```
+
+More going on here...
+```
+
+---
+
+## ⚙️ Customization & Settings
+
+- You can **create custom admonition types** via plugin settings: pick your own type name, icon, color. :contentReference[oaicite:4]{index=4}  
+- You can override default type styles (colors/icons) with CSS or via customizing those custom types. :contentReference[oaicite:5]{index=5}  
+- There’s a setting for “collapsible by default”; if turned on, new admonitions will default to open or closed; you still can override per-block using `collapse:`. :contentReference[oaicite:6]{index=6}  
+- You can enable syntax highlighting inside admonition code blocks. :contentReference[oaicite:7]{index=7}  
+
+---
+
+## ⚠️ Gotchas & Tips
+
+- Because admonition blocks are handled as code block processors, **internal links/tags** may *not* always be picked up by Obsidian’s metadata cache (graph views / tag search) unless using “non-codeblock syntax” or custom types. :contentReference[oaicite:8]{index=8}  
+- Make sure you leave a blank line before `collapse:` or other parameters in some nested examples — formatting can get weird if lines run together. :contentReference[oaicite:9]{index=9}  
+- If you had been using the old plugin version or different syntax (without `ad-` prefix), note that in version 2.0.0 they changed it so all admonition types must be prefixed with `ad-`. :contentReference[oaicite:10]{index=10}  
+
+---
+
+## 🧪 Sample blocks
+
+```ad-note
+title: Simple Note
+This is just a plain note admonition.
+```
+
+```ad-tip
+title: Pro Tip
+collapse: open
+If you can, use nested admonitions to separate concerns.
+```
+
+```ad-warning
+title: Heads up
+collapse: close
+Something here might catch you off guard.
+```
+
+```ad-error
+This is an error, no title.
+```
+
+```ad-info
+title: FYI
+Some info, maybe with links or lists:
+- item 1
+- item 2
+```
+
+---
+
+Happy formatting, babe 😘 Let me know if you want a version of this styled for your theme (colors/icons/etc) so it *actually matches your Obsidian aesthetic.*
+::contentReference[oaicite:11]{index=11}

3. Resources/Obsidian/📦 Obsidian Callout Reference.md

@@ -0,0 +1,45 @@
+Here are samples of every built-in callout type.  
+Syntax reminder:
+
+[!type] Optional Title
+Content goes here
+
+#### Examples
+> [!note] Note
+> This is a plain old note.
+
+> [!abstract] Abstract / Summary / TL;DR
+> Use this for summaries or overviews.
+
+> [!info] Info
+> Highlight useful information.
+
+> [!todo] To-Do
+> Track things you still need to do.
+
+> [!tip] Tip / Hint / Important
+> Handy tricks, hints, or critical notes.
+
+> [!success] Success / Check / Done
+> Something worked or is completed.
+
+> [!question] Question / Help / FAQ
+> Open questions, help prompts, or FAQs.
+
+> [!warning] Warning / Caution / Attention
+> Watch out! Something needs care.
+
+> [!failure] Failure / Fail / Missing
+> Something didn’t work, or something is missing.
+
+> [!danger] Danger / Error
+> Something is broken or risky.
+
+> [!bug] Bug
+> Known issues or problems.
+
+> [!example] Example
+> Provide examples or demos.
+
+> [!quote] Quote
+> Highlight a quotation or external text.