Editorial Policy

CDL Drill & Review follows an editorial policy designed for non-official study products. The site should be useful, clear, and reviewable. It should not sound more official than it is, and it should not hide behind thin support pages.

1. Study clarity over theatrics

Content should help the learner understand the practice loop, not overwhelm them with empty educational tone. A study page should produce a better next action, not a vague feeling of productivity.

2. Non-official boundary rule

The site must remain visibly non-official in its language and structure. If wording could make a learner confuse the product for an official provider, that wording should be corrected.

3. Maintenance obligations

Metadata, footer trust links, author identity, privacy, terms, cookies, contact, disclaimer, and methodology pages are part of editorial maintenance because they shape how the product is interpreted by both users and review systems.

4. Correction handling

When a material issue is found, the preferred sequence is confirm, repair, re-check the hosted result, and update any related trust language. A note in a backlog is not considered completion if the learner-facing page still looks wrong.

5. Product-finish standard

A page that technically loads but still feels skeletal, anonymous, or misleading does not meet this editorial policy. The site is expected to feel maintained as a whole, not merely assembled.

6. Trust-page density rule

Privacy, terms, cookies, contact, author identity, and disclaimer pages must not be treated as checkbox pages. They should carry enough density and specificity that a human reviewer can tell the site was maintained deliberately.

7. Product family rule

Core pages, support pages, and policy pages are reviewed as one family. A polished practice flow cannot excuse an anonymous or underwritten trust layer.

6. Trust-page density rule

Privacy, terms, cookies, contact, disclaimer, author identity, and methodology pages should carry enough density and specificity that a reviewer can tell the legal and identity layer was written for this site, not borrowed from a generic shell.

7. Product-family review rule

Practice pages, support pages, and trust pages are reviewed as a family. Strong question flow does not excuse weak authorship, weak contact language, or a policy layer that feels anonymous.

8. Review-surface rule

Every public page is part of the site’s review surface. If a page loads but still feels underwritten, identity-poor, or visually like boilerplate, the product is not considered finished for high-trust review purposes.