Test Post: Article Rendering

This is a mock article used to verify that all rendering components work correctly before publishing real content.

Introduction

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. This paragraph tests basic body text rendering, line height, and max-width behavior.

A second paragraph with a hyperlink example and bold text, italic text, and inline code to verify inline formatting.

Code Blocks

Python example:

def detect_injection(prompt: str) -> bool:
    suspicious_patterns = [
        "ignore previous instructions",
        "disregard your system prompt",
        "you are now",
    ]
    return any(p in prompt.lower() for p in suspicious_patterns)

Bash example:

# Check IAM bindings on a GCP project
gcloud projects get-iam-policy my-project \
  --flatten="bindings[].members" \
  --format="table(bindings.role, bindings.members)"

YAML example:

name: Deploy
on:
  push:
    branches: [main]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: bundle exec jekyll build

A Subheading

A Third-Level Heading

Nested headings should maintain a clear visual hierarchy without competing with the article title.

Blockquote

The most dangerous vulnerabilities are not the ones we know about — they are the ones we have not thought to look for yet.

Table

List

Unordered:

• Indirect prompt injection via untrusted document content
• Tool call hijacking through malicious tool descriptions
• Context window poisoning across multi-agent pipelines

Ordered:

1. Map all external data sources the agent reads
2. Identify which sources can be written by untrusted parties
3. Treat every untrusted input as a potential injection vector

Conclusion

If this post renders correctly — headings, code blocks with syntax highlighting, table, blockquote, lists, and inline formatting — the article system is ready for real content.