Template Overview

The third tier of Tiago Forte’s PARA system is Resources: reference materials, cheat sheets, code snippets, tool recommendations, and design patterns that support your ongoing interests and future projects.

Without structural discipline, a Resource folder becomes a messy junk drawer where web clips and PDFs are dumped and forgotten. An effective Resource note acts as an active library: carefully filtered, annotated with personal utility notes, and categorized for instant retrieval.

This template provides a comprehensive Resource library structure: topic overview, foundational guides, curated tool and software directories, code and configuration snippets, recommended reading lists, and vault project cross-references.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Resource: [Topic / Domain Reference Library]"
date: [YYYY-MM-DD]
type: "para-resource"
domain: "[Software / Design / Finance / Science / Craft]"
status: "Living Library"
curator: "[Your Name]"
tags: [para, pkm, resources, reference, second-brain]
---

# Resource: [Topic / Domain Reference Library]

## 1. Topic Scope & Value Proposition
- **Domain Definition:** What specific field, language, technology, or craft does this collection curate?
- **Why It Matters to My Vault:** In what active projects or areas will this reference material be deployed?

## 2. Foundational Specs, RFCs & Authoritative Documentation
| Resource Name | Type / Format | Primary Utility | URL / Reference |
| :--- | :--- | :--- | :--- |
| **Official Documentation** | Web Guide | Primary API spec and language reference | `https://example.com/docs` |
| **Standard RFC Spec** | Standards Doc | Formal protocol invariants | `RFC 9110` |
| **Community Style Guide** | Markdown Doc | Idiomatic code conventions | [[Internal-Style-Guide]] |

## 3. Essential Tools, Libraries & Frameworks
- **[Tool / Package 1]:** High-performance CLI utility for data transformation.
  - *Best for:* Large-scale stream processing.
- **[Tool / Package 2]:** Minimalist embedded database engine.
  - *Best for:* Offline-first local persistence.
- **[Tool / Package 3]:** Linting and static analysis tool.
  - *Best for:* Enforcing stylistic invariants in CI pipelines.

## 4. Reusable Code Snippets & Configuration Scaffolds
```bash
# Common high-leverage terminal command pattern
find . -type f -name "*.md" -print0 | xargs -0 grep -l "DRAFT"
# Recommended default configuration
[engine]
mode = "strict"
timeout_ms = 5000
cache_size_mb = 128

5. Curated Reading List & Benchmark Studies

  • [[Literature-Foundational-Book-A]] — The definitive text on this paradigm.
  • [[Literature-Empirical-Paper-B]] — Benchmark evaluation proving sub-5ms performance.

6. Projects & Areas Supported by This Resource

  • Linked Active Projects: [[Project-Name-Alpha]]
  • Linked Areas of Responsibility: [[Area-Name-Beta]]

## Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

```markdown
---
title: "Resource: Modern CommonMark & Markdown Parsing Engines"
date: [YYYY-MM-DD]
type: "para-resource"
domain: "Software Engineering & Text Processing"
status: "Living Library"
curator: "Elena Rostova"
tags: [para, pkm, resources, reference, second-brain]
---

# Resource: Modern CommonMark & Markdown Parsing Engines

## 1. Topic Scope & Value Proposition
- **Domain Definition:** High-performance, compliant CommonMark and GitHub Flavored Markdown (GFM) parsers, Abstract Syntax Tree (AST) transformers, and static site generators.
- **Why It Matters to My Vault:** Serves as the technical reference library for building local document indexing tools and our internal publishing pipeline.

## 2. Foundational Specs, RFCs & Authoritative Documentation
| Resource Name | Type / Format | Primary Utility | URL / Reference |
| :--- | :--- | :--- | :--- |
| **CommonMark Spec v0.31.2** | Formal Spec | Definitive parsing algorithms and boundary tests | `https://spec.commonmark.org` |
| **GFM Extension Spec** | Web Standard | Tables, task lists, and autolink extensions | `https://github.github.com/gfm` |
| **Unified / Remark AST** | Ecosystem Spec | Syntax tree format for Node.js processors | `https://github.com/syntax-tree/mdast` |

## 3. Essential Tools, Libraries & Frameworks
- **Comrak (Rust):** Compliant CommonMark parser with GFM extensions.
  - *Best for:* Native CLI utilities requiring extreme throughput (>50 MB/s text parsing).
- **Pulldown-cmark (Rust):** Pull-based event-driven Markdown parser.
  - *Best for:* Memory-constrained embedded pipelines.
- **Remark (JavaScript/TypeScript):** Ecosystem for AST manipulation.
  - *Best for:* Custom Astro and Next.js content pipeline plugins.

## 4. Reusable Code Snippets & Configuration Scaffolds
```rust
// Basic fast parsing with Comrak in Rust
use comrak::{markdown_to_html, Options};

let mut options = Options::default();
options.extension.table = true;
options.extension.tasklist = true;
let html = markdown_to_html("# Hello World\n- [x] Done", &options);

5. Curated Reading List & Benchmark Studies

  • [[Lit-Gruber-2004-Markdown-Original-Syntax]] — The original 2004 philosophy of readable plain text.
  • [[Lit-MacFarlane-2014-CommonMark-Specification]] — Why standardizing ambiguous corner cases mattered.

6. Projects & Areas Supported by This Resource

  • Linked Active Projects: [[Project-Launch-Templates-Gallery]]
  • Linked Areas of Responsibility: [[Area-Core-Web-Performance]]

## When to Use and When to Avoid

### When to Use
- Building reference libraries for ongoing technical or intellectual interests in PARA.
- Curating reusable code snippets, configuration scaffolds, and CLI one-liners.
- Assembling authoritative links to official RFC specifications and language documentation.
- Supporting active projects with pre-filtered, verified technical knowledge.

### When to Avoid
- Tracking time-sensitive projects with firm deadlines (use a Project dashboard).
- Managing personal habits or fitness health goals (use an Area standard note).
- Writing temporary meeting minutes or daily standup logs.
- Recording atomic ideas that belong in your permanent slip-box.

## On-Device AI Integration

Curate PARA Resource libraries with Oyma on macOS:

```markdown
Analyze the reference material, technical links, and code snippets:
1. Synthesize the domain scope and clarify why this collection matters to the vault.
2. Structure the authoritative documentation table with RFCs and official specifications.
3. Curate essential tools and libraries with concise practitioner use-case notes.
4. Formulate reusable configuration blocks and map cross-references to active projects.
Output in clean, structured CommonMark.

Your curated reference collections and engineering resources remain completely private on your Mac.

Frequently Asked Questions

What constitutes a Resource in the PARA method?

A Resource is a topic or theme of ongoing interest that you want to reference in the future (e.g., Typography, Rust Programming, Cryptography, Coffee Roasting).

How does a Resource differ from an Area?

An Area comes with personal responsibility and standards to maintain; a Resource is curated interest or reference material with no personal standard or deadline.

How does Oyma enhance PARA Resource libraries?

Oyma provides instant full-vault search across all curated resources with syntax-highlighted code blocks and zero cloud latency.