The docmd 0.6.7 release brings a massive upgrade to our landing-page capabilities with the introduction of the new Hero 2.0 component, alongside crucial stability patches for our build infrastructure and container parsing logic.

✨ Highlights

🚀 Landing Page Revolution & Hero

We’ve significantly empowered No-Style Pages (docmd’s answer to landing pages). You can now selectively re-enable the core menubar and scripts while maintaining a blank canvas, allowing you to build high-fidelity entry points that feel deeply integrated with your documentation.

To make building those pages effortless, we are introducing the Hero Container. Designed for high-impact visual storytelling, this component automatically renders stunning, responsive hero sections. It supports advanced features like layout:split for side-by-side media, layout:slider for interactive carousels, and glow:true for premium visual effects.

🍱 Enhanced Embed Ergonomics

We’ve updated the ::: embed syntax to be more flexible, now supporting optional brackets or quotes around the URL (e.g., ::: embed [url] or ::: embed "url"), improving structural consistency and developer ergonomics.

📝 Complete Changelog

🛠️ Core UI & Build Patches

• Hero Integration: Added the powerful new ::: hero markdown component with split and slider layout generation.
• Container Depth Tracking Fix: Resolved a critical parsing bug where single-line containers (like ::: button and ::: embed) would corrupt the depth tracking of parent containers, breaking complex nested layouts.
• Markdown Rendering on No-Style Pages: Fixed a regression where noStyle: true bypassed the markdown engine, ensuring core components like buttons and callouts work as expected on custom pages.
• Enhanced Component Opt-in: Added menubar: true and spa: true toggles for noStyle pages, giving developers granular control over the landing page environment.
• Live Build Source Fallback: Implemented an automated asset discovery resolver that gracefully falls back to looking for build components in the dist/ folder when the package is installed as a pure NPM dependency.

Migration Guide

No breaking changes. You can upgrade safely without altering any of your existing markdown content!