Statamic Safe Entities Laravel Package

Product Decisions This Supports

• Evaluate adopting a Statamic-native safety layer for entity handling/escaping in templates and content output. This is most relevant for sites with editor-supplied or user-generated content where incorrect entity handling can cause broken rendering or unsafe output.
• Roadmap: version 0.2.2 explicitly removes auto-hyphenation. Treat hyphenation as out of scope for this package; if the product needs automatic hyphenation, use CSS (hyphens, overflow-wrap) or a separate solution rather than planning around this addon.
• Build vs buy: adopt this package for a narrow “safe entities” concern, not as a general typography or sanitization layer. The removed auto-hyphenation dependencies reduce surface area and make the package easier to justify as a focused addon.
• Use cases: Statamic marketing sites, blogs, documentation, and multi-author CMS setups where template/content output needs safer entity handling and the team wants to avoid custom escaping logic.

When to Consider This Package

• Consider it if you run Statamic, need safer entity handling/escaping in Antlers or content output, and do not depend on auto-hyphenation.
• Consider it if the alternative is maintaining custom entity-escaping snippets across templates, or if you want a small, focused addon rather than a broader content-processing dependency.
• Look elsewhere if auto-hyphenation is a required product feature, if you need full HTML sanitization/WYSIWYG security (use a dedicated sanitizer), if you are not on Statamic, or if the team cannot accept addon-specific dependencies.
• Existing users on 0.2.1 who rely on auto-hyphenation should pin the prior version or plan a migration before upgrading. Validate rendered content after upgrade because this is a breaking change.

How to Pitch It (Stakeholders)

• Executives: a narrow Statamic addon that helps protect content rendering with less custom code. Release 0.2.2 simplifies the package by removing auto-hyphenation, reducing dependency surface and clarifying its purpose.
• Engineering: the breaking change removes auto-hyphenation and related dependencies. Upgrade only after confirming no templates or content pipelines rely on that behavior. Keep using this for safe entity handling if needed; handle hyphenation via CSS or a separate tool. It is a targeted adoption candidate, not a general content-security or typography solution.