editorial-help

Tracking editorial workflow across multiple sites is done by generating per-site summaries for content lifecycle stages including ideas, planned, drafting, review, and published posts. It provides a centralized content calendar view for improved governance.

Report content lifecycle stages by running the editorial-status command to synthesize calendar data per site. It exposes a unified dashboard view showing current stages from ideas through published content across configured sites.

No external dependencies are required to generate multi-site editorial calendar reports. It relies solely on site frontmatter and configured calendar files to output structured data suitable for vector embedding.

Yes, you can use site frontmatter and configured calendar files to coordinate content governance and deadlines. It synthesizes this data to ensure visibility into content movement and improve on-time publication across sites.

Yes, multi-site editorial reporting outputs structured data suitable for vector embedding. By processing frontmatter and calendar files, it generates per-site summaries of the full content lifecycle that can be embedded for downstream retrieval.

Editorial workflow visibility is limited to the data present in site frontmatter and configured calendar files. Content movement tracking depends on accurately maintained frontmatter for the audiocontrol and editorialcontrol sites to generate valid per-site summaries.