This is a comprehensive test post for the notch.org blog. It exercises every markdown element and Obsidian Publish feature so you can see how the Solarized Dark monospace theme renders everything. Delete this when you’re done tweaking.
Typography
Regular paragraph text. The body uses IBM Plex Mono at 15px with 1.7 line-height. This should feel clean, technical, and easy to scan. Long paragraphs should wrap nicely within the 760px content width without feeling cramped.
Here’s text with bold, italic, bold italic, strikethrough, and highlighted text. You can also use inline code to reference things like kubectl get pods or file paths like /etc/nginx/nginx.conf.
“The best way to predict the future is to invent it.” — Alan Kay
Heading 3 — Subsection
Regular content under an H3. Notice the heading hierarchy: H1 is the page title (set by Publish), H2 gets a bottom border for visual separation, H3 is slightly smaller.
HEADING 4 — CATEGORY LABEL
H4-H6 are styled as uppercase labels — good for minor section markers within longer posts.
This is a simple blockquote. It should have a left border accent and slightly muted text color.
Multi-line blockquote
Sometimes you need to quote a longer passage. This tests how the blockquote handles multiple paragraphs and inline formatting like italics and code.
— Attribution goes here
Nested blockquotes:
Can go deeper
And even deeper still
Callouts
A Note
Notes are for general information that supplements the main content. Good for “by the way” moments.
Pro Tip
Use callouts sparingly — they lose impact if overused. Reserve them for genuinely useful information.
Security Warning
Never store API keys in client-side code or public repositories. Use environment variables or a secrets manager.
Critical
This action is irreversible. Deleted data cannot be recovered.
Technical Context
Obsidian Publish serves content via a CDN with automatic HTTPS. Sites are indexed by search engines by default, but you can disable this in site settings.
TL;DR
Solarized Dark + IBM Plex Mono = readable technical blog that doesn’t burn your retinas.
Example Configuration
server: host: 0.0.0.0 port: 8080 tls: true
FAQ: Can I use custom JavaScript?
Yes, but only with a custom domain. Place publish.js in your vault root.
Deployment Complete
Your site is live at notch.org. DNS propagation may take up to 48 hours.
Build Failed
Check your publish.css for syntax errors. Invalid CSS will be silently ignored.
Known Issue
Community plugin codeblocks (Dataview, etc.) do not render on Publish.
Code
Inline
Use docker compose up -d to start services, or check status with systemctl status nginx.
Fenced Code Blocks
# Simple threat scoring modeldef calculate_risk(indicators: list[dict]) -> float: """Score a set of threat indicators on a 0-1 scale.""" weights = { "malware_hash": 0.9, "suspicious_domain": 0.7, "unusual_login": 0.5, "port_scan": 0.3, } total = sum( weights.get(ind["type"], 0.1) * ind.get("confidence", 0.5) for ind in indicators ) return min(total / len(indicators), 1.0) if indicators else 0.0
-- Monthly active users by cohortSELECT DATE_TRUNC('month', created_at) AS cohort_month, DATE_TRUNC('month', event_date) AS activity_month, COUNT(DISTINCT user_id) AS active_usersFROM user_eventsWHERE event_type = 'login'GROUP BY 1, 2ORDER BY 1, 2;
Tables
Simple Table
Tool
Category
License
Obsidian
PKM
Commercial
Hugo
Static Site
Apache 2.0
Ghost
CMS
MIT
Notion
Productivity
Commercial
Wider Table
Threat Type
Severity
MITRE ATT&CK
Detection Method
Response Time
Ransomware
Critical
T1486
EDR + SIEM correlation
< 15 min
Phishing
High
T1566
Email gateway + user report
< 1 hour
Insider Threat
High
T1078
UEBA + DLP
< 4 hours
Supply Chain
Critical
T1195
SBOM analysis + monitoring
< 24 hours
Port Scanning
Low
T1046
IDS/IPS
Automated
Images
Images display with a subtle border and rounded corners. Test with an external image:
Caption: Use italic text below images for captions.
Horizontal Rules
Three different separators above, between sections, and below. They render as dashed lines.
Footnotes
This claim needs a source1. And here’s another reference2.
Math (LaTeX)
Inline math: The time complexity is O(nlogn) for the average case.
Here’s a quick reference for useful frontmatter properties on your blog posts:
---# Requiredpublish: true# Recommended permalink: blog/your-url-slugdescription: "One-line summary for SEO and social cards"tags: - ai - security - strategy# Optional — Social previewscover: "Attachments/cover-image.png" # or external URLimage: "https://example.com/og.png"# Optional — Navigationaliases: - Alternate Title - Short Name# Optional — Stylingcssclasses: - wide-page # if you define custom classes# Auto-exclude from publish# publish: false---
Blog Post Template
Here’s a starter template for actual posts. Copy this structure:
---publish: truepermalink: blog/your-slug-heredescription: "Brief description for SEO and social sharing"tags: - topic1 - topic2---# Post Title*Brief italicized lede or subtitle.*---## The SetupOpening section — establish the problem or context.## The AnalysisCore content. Use code blocks, tables, callouts as needed.## The TakeawayWhat should the reader do with this information?---*Published on notch.org. Views are my own.*
That’s Everything
If all the above renders cleanly in your Solarized Dark monospace theme, you’re good to go. The elements tested:
Headings (H1-H6)
Paragraphs and inline formatting
Links (internal, external, unresolved)
Lists (ordered, unordered, task, mixed)
Blockquotes (single, multi, nested)
Callouts (11 types including foldable)
Code blocks (6 languages + inline)
Tables (simple + wide)
Images (external)
Horizontal rules
Footnotes
Math/LaTeX
Tags
Properties/frontmatter
Embeds (syntax reference)
Delete this post once you’re happy with the theme. Or keep it as a style guide.
Footnotes
Source: “The Art of Computer Programming” by Donald Knuth, 1968. ↩
According to the 2025 Verizon Data Breach Investigations Report. ↩