Siteleaf gives editors control over structured content, but the hardest work is often knowing what is still current before a new entry goes live. Strawberry can review collections, linked pages, media references, and publication status to assemble an editorial queue grounded in the actual site.
01
Treat a collection as an editorial system, not a folder of entries.
A collection can contain fresh articles beside old pages that still win search traffic and point visitors toward the wrong action. Strawberry can examine the related items, their links, and their role in navigation before the next edit makes the inconsistency more visible.
02
Catch media and link failures before a reader does.
An entry may save successfully while its hero image, document link, or referenced page is no longer available. Strawberry can test those references and put the result beside the entry that needs a correction.
03
Make publishing readiness explicit.
An incomplete description, ambiguous owner, or unverified scheduled date should not be discovered after publication. Strawberry can prepare a short preflight list so editorial judgment happens before the status changes.
04
Close Friday with next week’s publishing queue already checked.
A Friday afternoon pass gives editors a chance to repair links and clarify ownership before a Monday deadline creates unnecessary pressure. Strawberry can gather the evidence and leave every publishing switch untouched.
It can inspect the signed-in Siteleaf content and prepare an evidence-based list of stale entries, broken references, and related-page conflicts.
It can prepare a preflight view covering metadata, ownership, dates, and linked assets for review.
It creates a repair window before the following week’s publishing schedule starts.
Before Siteleaf content changes, review the entry status, scheduled date, source material, linked media, and every page whose navigation or references it affects.
Siteleaf Strawberry