Editorial Policy

Each recipe starts from a vertical operating question. Dashcipe defines the decision before the visual layout.

Recipes should include recommended KPIs, data sources, removal rules, failure signals, and layout intent.

Primary KPIs must be actionable within a weekly review cycle.

Attractive but non-actionable vanity metrics are moved out of the primary KPI row or treated as supporting signals.

Dashcipe may use AI tools for drafts, but human review checks meaning, accuracy, duplication, and practical value before publication.

AI-generated code and prompts are reviewed for feasibility, accessibility, state UI, and schema fit.

Public previews from template marketplaces are used only to understand general information architecture, widget mixes, density, and navigation patterns.

Dashcipe does not use paid template files, images, screenshots, code, unique copy, or proprietary color systems.

Broken links, inaccurate explanations, and outdated implementation patterns are corrected when found.

New Starter Kits and recipes are prioritized by request volume, search demand, operating value, and implementation difficulty.