Blog

A content creation toolkit for drafting, editing, optimizing, scheduling, and managing blog content workflows — all from the command line with timestamped local logging.

Commands

Each content command (draft, edit, optimize, etc.) works the same way:

• - With arguments: saves the entry with a timestamp to its dedicated .log file and records it in activity history
• Without arguments: displays the 20 most recent entries from that command's log

Data Storage

All data is stored locally in plain-text log files:

CODEBLOCK0

Each entry is stored as YYYY-MM-DD HH:MM|<value> for easy parsing and export.

Requirements

• - Bash 4.0+ (uses set -euo pipefail)
• Standard UNIX utilities: date, wc, du, grep, head, tail, INLINECODE28
• No external dependencies or API keys required
• Works offline — all data stays on your machine

When to Use

1. 1. Blog content pipeline — Track a post from draft → outline → edit → optimize → schedule in one place with timestamps, so you always know where each piece stands
2. SEO workflow — Log optimization notes, headline variants, and hashtag sets for each post, then search or export them later for analysis
3. Editorial calendar — Use schedule to record publication dates and recent to see upcoming deadlines at a glance
4. Multi-language content — Track translations with translate, tone adjustments with tone, and rewrites with rewrite to manage localized content
5. Social media prep — Build a library of hooks, CTAs, and hashtag sets that you can search and reuse across posts

Examples

Full blog post workflow

CODEBLOCK1

Social media preparation

CODEBLOCK2

Review and export

CODEBLOCK3

Rewrite and translate

CODEBLOCK4

Output

All commands print confirmation to stdout. Data is persisted in ~/.local/share/blog/. Use blog stats for an overview, blog search <term> to find specific entries, or blog export <fmt> to extract all data as JSON, CSV, or plain text.