Sanitization policy

This site is designed to share engineering patterns and outcomes without exposing proprietary details.

Rules

• No proprietary code or internal system names.
• No internal URLs, hostnames, ticket IDs, or cluster identifiers.
• No confidential business metrics, customer data, or private contracts.
• Case studies focus on patterns, decisions, and lessons.

Publishing checklist

1. Remove or replace sensitive names with neutral equivalents.
2. Keep impact statements as ranges or qualitative deltas where needed.
3. Avoid screenshots that reveal internal labels.
4. Verify links and metadata do not leak private information.
5. Mark sanitized content with the Sanitized badge.

Optional build-time blocklist

Set SANITIZATION_BLOCKLIST=true before build to enforce keyword checks.

Use SANITIZATION_BLOCKLIST_KEYWORDS to provide custom comma-separated blocked terms.

SANITIZATION_BLOCKLIST=true npm run build

The build will fail if a sanitized document contains blocked terms.