Markdown Field Type Laravel Package

Product Decisions This Supports

• Build vs. buy for content authoring. The package is a ready-made Markdown field type for the Streams Platform (Anomaly Labs/PyroCMS ecosystem). It answers a recurring "do we build an editor?" question with a small, MIT-licensed addon instead of custom work.
• Admin UX investment in content workflows. Adopting it signals that Markdown is a first-class authoring format for entry types — relevant for blog posts, documentation, changelogs, release notes, and internal knowledge bases managed inside a CMS.
• Platform extensibility bet. Because it is a Streams field type, evaluating it doubles as a low-cost test of how far the field-type architecture carries us before we need custom admin UI.
• Roadmap scoping. If content ops are on the roadmap, this addon lets us ship Markdown authoring in a sprint rather than funding an editor project; it keeps the "rich text vs. Markdown vs. WYSIWYG" decision reversible at low cost.
• Ecosystem dependency mapping. With 3 stars and 0 dependents, this is a single-vendor utility, not a community standard. That informs whether we treat Streams addons as a supported dependency class or as one-off conveniences.

When to Consider This Package

Consider it when:

• You are already running the Streams Platform / PyroCMS and need Markdown entry authoring without building a field type.
• Your authors are comfortable with Markdown and you want plain-text, diff-friendly, version-control-friendly content.
• You want the smallest possible dependency: same vendor as the platform, MIT license, narrow surface area, no new runtime libraries.
• You can own rendering and sanitization yourself (or already have a trusted pipeline), since a thin field type should not be assumed to be a security boundary.

Look elsewhere when:

• You are not on Streams — this is ecosystem-specific and offers no value on vanilla Laravel.
• You need WYSIWYG, collaborative editing, or a modern editor component; this is a Markdown field type, not a rich-text suite.
• You require a maintained, widely adopted dependency with an active community. Three stars, zero dependents, and minimal activity imply a low bus factor and no external support path.
• You need guaranteed XSS-safe rendering out of the box, plugin ecosystems, or accessibility commitments — those must be verified in code or supplied by us.

Treat it as a tactical addon to pilot and pin, not a strategic platform commitment.

How to Pitch It (Stakeholders)

For executives: This is a small, free, MIT-licensed addon that gives editors Markdown authoring directly inside our CMS admin. It costs effectively nothing to trial, carries no licensing or lock-in risk, and can be adopted or dropped without affecting the wider product. It is a convenience, not a strategic bet — the recommendation is a timeboxed pilot, not a platform decision.

For engineering: It is a standard Streams field type — drop-in, no new runtime dependencies, limited code surface. The trade-off is maturity: minimal adoption and activity means we own the support burden, the rendering pipeline, and XSS sanitization on output. Pin the version, wrap it with our own tests, and keep the integration thin so it stays swappable.

Recommendation: Pilot on one internal content type with a two-week evaluation window. Success criteria are author adoption and zero rendering/sanitization incidents; anything beyond that should trigger a build-vs-buy review rather than further investment in this package.