1 min read · 216 words
This is a test post to verify the blog infrastructure is working correctly. It includes code blocks, a Mermaid diagram, and various formatting elements.
Code Highlighting Test
Here is a Python code sample rendered with Prismatic/Prism.js:
class Engine:
"""Business rule execution component."""
def calculate_pricing(self, order: Order) -> Decimal:
base = order.quantity * order.unit_price
discount = self._apply_volume_discount(base, order.quantity)
return base - discount
def _apply_volume_discount(self, total: Decimal, qty: int) -> Decimal:
if qty >= 100:
return total * Decimal("0.15")
elif qty >= 50:
return total * Decimal("0.10")
return Decimal("0")
And a TypeScript example:
interface FlowComponent {
readonly id: string;
readonly interactions: InteractionComponent[];
execute(context: FlowContext): Promise<FlowResult>;
}
const checkoutFlow: FlowComponent = {
id: "checkout",
interactions: [cartReview, paymentEntry, confirmation],
async execute(ctx) {
for (const step of this.interactions) {
const result = await step.run(ctx);
if (!result.success) return FlowResult.abort(result.reason);
}
return FlowResult.complete();
}
};
Mermaid Diagram Test
A component communication diagram:
graph TD
M[Manager] --> E1[Engine A]
M --> E2[Engine B]
M --> RA[Resource Accessor]
E1 --> RA
E2 --> RA
U[Utility] -.-> M
U -.-> E1
U -.-> E2
U -.-> RA
Formatting Tests
This verifies bold, italic, inline code, and internal links all render correctly in the blog post template.
- Bullet point one
- Bullet point two with
code - Bullet point three
Systems with correct boundaries produce testable systems. Systems with incorrect boundaries produce test friction.