SifrBolt / docs

SifrBolt Documentation

Documentation to understand the SifrBolt platform and use it effectively.

Goal

Use this guide to balance personalized components with aggressive caching. You will configure allow/deny lists, rollout the changes safely, and validate the results.

Prerequisites

  • Surge or higher plan with the Performance Pack enabled.
  • Redis or compatible object cache connected to your WordPress stack.
  • Console access with permission to edit cache policies and rollout rings.

Step 1 · Assess Your Page Structure

  1. Identify the blocks on your PDPs that require fresh data each request (e.g., cart widgets, low-inventory banners).
  2. List the components that can be cached—catalog metadata, pricing tables, recommendation carousels.
  3. Capture baseline metrics for TTFB and conversion so you can compare after rollout.

Step 2 · Configure Adaptive Cache

  1. In the console, open Cache Policies → Adaptive Cache for the target storefront.
  2. Add volatile routes or fragments to the Deny list and cache-friendly ones to the Allow list.
  3. Enable Stale-While-Revalidate (SWR) and set the refresh interval that matches your catalog updates.
  4. Save the draft and request signatures if your workspace requires approval.

Step 3 · Roll Out Safely

  1. Create rollout rings (10% → 50% → 100%) so you can compare performance at each stage.
  2. Promote the policy through the rings, monitoring latency and error rates in the console dashboards.
  3. If you surface anomalies, pause the rollout and adjust the allow/deny lists; relaunch after validation.

Step 4 · Validate the Results

Verification

  1. Download bundle adaptive-cache-2025-01 from the Trust Center (Performance Packs → Recipes).
  2. Use the verification CLI to confirm the signed configuration (for example bunx @sifrbolt/verify rollout --bundle adaptive-cache-2025-01).
  3. Compare pre/post metrics attached to the bundle or export your own from the console timeline.

Follow-Up Actions

  • Share the validated metrics with stakeholders using the Launch Summary template included in the bundle.
  • Replicate the configuration across other storefronts, adjusting allow/deny lists to match local content.
  • Combine adaptive caching with the Image IQ feature pack to extend gains to media-heavy PDPs.

Add additional cache and performance recipes under docs/src/pages/implementation/ as you expand coverage.