Changed folder naming.

This commit is contained in:
Alexander Kogutkiewicz
2025-09-21 22:26:43 -05:00
parent 837d0bb6ac
commit ac8a9e293b
114 changed files with 139 additions and 62 deletions

View File

@@ -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 youll 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}
- Theres 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 Obsidians 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}

View File

@@ -0,0 +1,81 @@
.
└── ITManager
├── 1. Projects
│   ├── 1. Active
│   │   ├── All-State Implementation
│   │   │   ├── 1. Meetings
│   │   │   ├── 2. Notes
│   │   │   ├── 3. Tasks
│   │   │   └── 4. Docs
│   │   ├── Epicor EDI Implementation
│   │   │   ├── 1. Meetings
│   │   │   ├── 2. Notes
│   │   │   ├── 3. Tasks
│   │   │   └── 4. Docs
│   │   ├── Inspection Plans
│   │   │   ├── 1. Meetings
│   │   │   ├── 2. Notes
│   │   │   ├── 3. Tasks
│   │   │   └── 4. Docs
│   │   ├── Maintenance Module
│   │   │   ├── 1. Meetings
│   │   │   ├── 2. Notes
│   │   │   ├── 3. Tasks
│   │   │   └── 4. Docs
│   │   │   └── Documents
│   │   └── Manager Role
│   ├── 2. Pipeline
│   └── 3. Completed
├── 2. Reference
│   ├── Access
│   │   ├── Portals
│   │   ├── Service Accounts
│   │   ├── SSO & MFA
│   │   └── System Logins
│   ├── Applications
│   │   ├── Cloud Services
│   │   ├── ERP
│   │   ├── Integrations
│   │   ├── Licensing
│   │   └── LOB Apps
│   ├── Contacts
│   │   ├── Emergency
│   │   ├── Internal
│   │   ├── IT Team
│   │   └── Key Business Users
│   ├── Knowledgebase
│   │   ├── Common Fixes
│   │   ├── Team SOPs
│   │   ├── Troubleshooting Trees
│   │   └── User FAQ
│   ├── Policies
│   │   ├── Change Management
│   │   ├── Compliance
│   │   ├── Incident Response
│   │   ├── Onboarding & Offboarding
│   │   └── Security
│   ├── Systems
│   │   ├── Backups and DR
│   │   ├── Copy Machines
│   │   │   └── Machines
│   │   ├── Firewall & VPN
│   │   ├── Monitoring
│   │   ├── Networking
│   │   ├── Servers & VMs
│   │   └── Shredding
│   │   └── Receipts
│   └── Vendors
│   ├── Contacts
│   │   └── Contacts
│   ├── Contracts & SLAs
│   ├── Procurement
│   └── Renewals
│   ├── Invoices
│   └── Quotes
├── 3. Daily Notes
├── 4. Meetings
├── 5. Archive
│   └── Notes
└── 9. System
├── Assets
└── Templates

View File

@@ -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 didnt 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.