# Ingeniux CMS Site Tree and Page Audit Instructions v2 ## Purpose Analyze an Ingeniux CMS page descendant export to identify actionable site tree and page cleanup issues. This report focuses on: - Outdated or stale pages - Unmarked content - Checked-out / working content - Start Date and End Date visibility governance - Abandoned drafts - Deep or confusing site tree hierarchy - Component-like content mixed into the page tree - Cleanup task generation ## Ingeniux Publish and Visibility Rules This audit must treat publish state and visibility state separately. ### Marked For Publish `Marked For Publish` controls whether an item is included in publishing output. If an item is not marked for publish, it will not appear on the live site, even if its Start Date arrives. ### Start Date `Start Date` controls when an already-published item is allowed to appear to visitors. It does not publish the item by itself. ### End Date `End Date` controls when an already-published item is hidden from visitors. It does not unpublish the item. An item can be past its End Date and still be marked for publish, which means it may continue to add publish overhead while providing no visitor-facing value. ## Required Detection Rules ### 1. End Date Passed but Still Publishing Detect: - `End Date < today` - AND `Marked For Publish = true` - Ignore default/unbounded End Date values such as `9999-12-31` Meaning: - The item is hidden from visitors - The item is still being published - It may increase publishing time or output size without live-site value Recommended action: - Unmark for publish if no longer needed - Archive the item - Delete only after appropriate review Priority: - High ### 2. Future Start Date but Not Marked for Publish Detect: - `Start Date > today` - AND `Marked For Publish = false` - Ignore default/unbounded Start Date values such as `0001-01-01` Meaning: - The item will not appear automatically when the Start Date arrives - The content may miss its intended launch window Recommended action: - Confirm whether the item should launch - Mark for publish if it should become visible at the Start Date - Review workflow/ownership Priority: - High ### 3. Unmarked Content Detect: - `Marked For Publish = false` Meaning: - Item is not being published - May be an abandoned draft, retired page, or valid work in progress Recommended action: - Review for archive/delete - Mark for publish if still needed Priority: - Medium ### 4. Checked-Out / Working Content Detect: - `Checked Out = true` Meaning: - Item is currently locked or in working state - May represent active work or abandoned editing Recommended action: - Confirm whether work is active - Check in, reassign, or archive if abandoned Priority: - Medium ### 5. Checked Out and Unmarked Detect: - `Checked Out = true` - AND `Marked For Publish = false` Meaning: - Strong abandoned-work signal - Often represents unfinished or stale content Recommended action: - Prioritize owner review - Check in or archive if no longer needed Priority: - High ### 6. Never Published and Older Than 90 Days Detect: - `Published` is blank/null - AND `Created` is more than 90 days old Meaning: - Likely abandoned draft, test content, migration remnant, or staging content Recommended action: - Review for archive/delete Priority: - Medium ### 7. Published but Not Recently Changed Detect: - `Marked For Publish = true` - AND `Changed` is more than 365 days old Meaning: - Potential stale live content - Not automatically bad, but useful for review Recommended action: - Review for accuracy, ownership, and continued relevance Priority: - Medium ### 8. Stale Unpublished Content Detect: - `Marked For Publish = false` - AND `Changed` is more than 180 days old Meaning: - Stale unpublished content is likely abandoned or no longer needed Recommended action: - Archive or delete after review Priority: - Medium ### 9. Deep Site Tree Placement Detect: - Calculated site tree depth exceeds the configured threshold, such as depth >= 5 Meaning: - May indicate unnecessary hierarchy, buried content, or confusing site organization Recommended action: - Review whether the hierarchy is meaningful - Simplify only when structure does not add value Priority: - Medium ### 10. Weak or Temporary Naming Flag names containing patterns such as: - test - copy - temp - draft - new - sample - placeholder - lorem Meaning: - Likely test content, migration leftovers, or unresolved naming Recommended action: - Rename, archive, or delete after review Priority: - Medium ### 11. Component-Like Schema in Page Tree Flag schemas or names that appear to represent reusable content mixed into the page tree. Examples may include schema names containing: - Tray - Component - CopyBlock - Alert - SiteControl - SearchNavigation - KeyMatch Meaning: - Reusable/non-page content may be mixed into page/navigation structures Recommended action: - Move to an appropriate component area or governance location Priority: - High ## Required Metrics Generate: - Total items - Actionable cleanup task count - Unmarked items - Checked-out items - Checked-out and unmarked items - Never published items older than 90 days - Published items not changed in more than 365 days - End Date passed but still publishing - Future Start Date but not marked for publish - Deep site tree items - Counts by issue type - Counts by schema - Counts by priority ## Required Excel Worksheets ### 1. Executive Summary Include: - Summary metrics - Issue distribution - Priority distribution - Visual charts ### 2. Site & Page Audit One row per item from the export. Recommended columns: - ID - Name - Schema - Parent ID - Calculated Depth - Checked Out - Marked For Publish - Created - Changed - Published - Start Date - End Date - Current Version - Detected Issues - Priority - Recommended Actions ### 3. Cleanup Tasks Only include rows with actionable issues. Do not include rows with no immediate issue. Recommended columns: - Priority - ID - Name - Schema - Issue / Task Type - Recommended Action - Status - Notes ### 4. Issue Flags One row per issue per item. Recommended columns: - ID - Name - Schema - Issue Type - Priority - Recommended Action - Notes ### 5. Schema Metrics Group by schema and include: - Total items - Issue count - Unmarked count - Checked-out count ### 6. Depth Metrics Group by calculated site tree depth. ### 7. Publish Lifecycle Include the corrected Ingeniux-specific scheduling rules: - End Date passed but still publishing - Future Start Date but not marked - Never published older than threshold - Unmarked content ### 8. Rules Document the logic used to generate the workbook. ## Required Visuals Create at minimum: - Issue distribution chart - Priority summary chart - Schema distribution chart - Site tree depth distribution chart ## Cleanup Task Rules Cleanup tasks should only be generated for rows with real issues. Do not add task rows for clean items. ## Key Principle In Ingeniux CMS, scheduled visibility and publish state are separate. - Marked For Publish determines whether content is published - Start Date controls when published content becomes visible - End Date controls when published content becomes hidden This means expired content can still create publishing overhead, and future scheduled content will not appear unless it is also marked for publish.