Laravel Laravel Package

Product Decisions This Supports

• Content authoring features: Whether to add Markdown as an input format for docs, blogs, knowledge bases, changelogs, release notes, and in-app help in a Laravel product.
• Build vs buy: Offloads Markdown parsing to an established PHP parser (Parsedown) instead of maintaining a custom parser; the Laravel wrapper (helper + Blade directive + singleton config) removes glue code and lowers integration cost.
• Feature scoping unlocked by 1.2.0: The second argument to parsedown() / @parsedown enables inline parsing of expressions, useful for CMS fields, email templates, and preview panes; argument-less calls return a configurable singleton, which simplifies repeated rendering (e.g., comment/post lists) and environment-specific behavior.
• Operational configurability: The publishable config file makes parser behavior a deploy-time decision (e.g., safe mode on in production, relaxed in tests) rather than a code change — a useful lever for security and QA.
• Risk/roadmap decisions: The PHP ≥ 7.2.3 floor narrows which apps can adopt now; rendering user-generated Markdown requires an explicit sanitization decision, not an afterthought.

When to Consider This Package

Consider it when:

• You run a Laravel app on PHP ≥ 7.2.3 and need lightweight Markdown → HTML rendering.
• Content is trusted or semi-trusted: admin-authored pages, internal docs, changelogs, README-style content.
• You want minimal integration surface: @parsedown in Blade, parsedown() in PHP, and singleton reuse for performance.
• You want config-driven parser behavior without editing application code.

Look elsewhere when:

• You need full CommonMark/GFM compliance — Parsedown has known spec deviations; league/commonmark is the more spec-faithful, actively maintained alternative.
• You need rich extensions (tables, footnotes, strikethrough) — likely requires ParsedownExtra or a different parser.
• You render untrusted user input at scale — pair with robust sanitization (e.g., HTMLPurifier) and prefer a parser with an active security-response process.
• You are on PHP < 7.2.3 (blocked by this release) or require vendor SLAs / long-term support guarantees.
• You need post-processing the thin wrapper doesn't provide, such as syntax highlighting, TOC generation, or custom AST manipulation.

How to Pitch It (Stakeholders)

Executives: This is a small, low-cost dependency that lets us ship Markdown-based content features (docs, blogs, in-app help) without building and maintaining a parser ourselves. Release 1.2.0 improves flexibility — inline parsing, a reusable configured singleton, and a publishable config file — and sets a PHP 7.2.3 minimum, which all current environments satisfy. Primary caution: for user-generated content we must enforce output sanitization, and we should track parser maintenance/security as an ongoing risk rather than assume it is handled.

Engineering: 1.2.0 adds a second argument to parsedown() and @parsedown for inline parsing, allows argument-less calls that return a configured Parsedown singleton, and introduces a publishable config file that controls that singleton. Minimum PHP is now 7.2.3. Recommended usage: centralize parser settings (including safe mode) in the published config, avoid rendering raw untrusted HTML, and rely on singleton reuse for list/preview rendering. Evaluate league/commonmark if strict CommonMark compliance or extension support becomes a requirement.