+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ $ls_faq ) : ?>
+
+
+
+
+
+
+
+
-
-
+
+
diff --git a/patterns/sections/phase-journey-nav.php b/patterns/sections/phase-journey-nav.php
index c0606f4..f5a8223 100644
--- a/patterns/sections/phase-journey-nav.php
+++ b/patterns/sections/phase-journey-nav.php
@@ -23,16 +23,19 @@
* passed down as a CSS custom property instead of a literal `color`, leaving the actual `color`
* property free for that external stylesheet to own per state.
*
- * IMPORTANT — insert this as a live reference, not a flattened copy: the "auto-detect active
- * phase" logic below only re-evaluates on every real front-end request if this pattern stays a
- * live `` reference block. WordPress's
- * normal "click to insert from the pattern library" flow instead flattens a file-registered
- * pattern into a static copy of whatever get_queried_object() resolved to at insertion time (which
- * is frequently no page at all, e.g. inside the REST endpoint that serves the inserter panel) —
- * baking in a permanently-wrong or permanently-blank active state that can never update again,
- * confirmed empirically while building this page. Use the pattern/reference block, or the Insert
- * Pattern flow if a future WP version changes this default, but verify the rendered HTML actually
- * contains "is-active" before treating a phase page as done.
+ * Active-state detection does NOT depend on this pattern staying a live reference. An earlier
+ * version computed the active step purely in PHP via get_queried_object(), which only re-evaluated
+ * on real front-end requests while the pattern stayed a live `wp:pattern` reference — WordPress
+ * routinely flattens a pattern into a frozen static copy the moment a page is opened in the
+ * editor, permanently baking in whatever active state existed at that moment (often wrong or
+ * blank), and re-attaching the live reference doesn't prevent it from being reflattened again on
+ * the next edit. The PHP below still computes `$ls_is_active` and adds an `is-active` class as a
+ * best-effort default, but the actual visual active/inactive treatment (link colour, dot
+ * visibility) is driven entirely by CSS keyed off a `page-slug-{slug}` body class — see
+ * ls_theme_add_phase_page_body_class() in inc/phase-page-body-class.php and the body-class rules
+ * in phase-journey-nav.scss. That body class is recomputed by WordPress core on every single
+ * request regardless of how this pattern's blocks are stored, so the correct step stays
+ * highlighted even if this instance is (or becomes) a flattened copy.
* Keywords: phase, journey, lifecycle, navigation, section
* Viewport Width: 1280
* Inserter: true
@@ -114,9 +117,7 @@
-
-
diff --git a/patterns/sections/phase-services-in-phase.php b/patterns/sections/phase-services-in-phase.php
new file mode 100644
index 0000000..9d6ff5f
--- /dev/null
+++ b/patterns/sections/phase-services-in-phase.php
@@ -0,0 +1,216 @@
+` reference block.
+ * Keywords: phase, discover, create, build, launch, grow, evolve, services, cards, section
+ * Viewport Width: 1280
+ * Inserter: true
+ *
+ * @package ls-theme
+ */
+
+$ls_phase_services_by_phase = array(
+ 'discover' => array(
+ array(
+ 'label' => __( 'Discovery', 'ls-theme' ),
+ 'description' => __( 'Stakeholder workshops, audits, scoping and feasibility — the evidence layer that comes before design or build.', 'ls-theme' ),
+ 'url' => '/services/discovery/',
+ 'icon' => 'search',
+ ),
+ ),
+ 'create' => array(
+ array(
+ 'label' => __( 'Content', 'ls-theme' ),
+ 'description' => __( 'Content modelling, editorial workflow and governance that holds up at scale.', 'ls-theme' ),
+ 'url' => '/services/content/',
+ 'icon' => 'file-text',
+ ),
+ array(
+ 'label' => __( 'Design', 'ls-theme' ),
+ 'description' => __( 'Design systems, accessible patterns and Figma→WordPress parity. Already a deeper page.', 'ls-theme' ),
+ 'url' => '/services/design/',
+ 'icon' => 'paint-brush',
+ ),
+ ),
+ 'build' => array(
+ array(
+ 'label' => __( 'Development', 'ls-theme' ),
+ 'description' => __( 'Block themes, WooCommerce, integrations and platform refactors built for long-term health.', 'ls-theme' ),
+ 'url' => '/services/development/',
+ 'icon' => 'code',
+ ),
+ array(
+ 'label' => __( 'Migrations', 'ls-theme' ),
+ 'description' => __( 'Audits, mapping and redirects that take legacy platforms apart without losing traction.', 'ls-theme' ),
+ 'url' => '/services/migrations/',
+ 'icon' => 'arrows-left-right',
+ ),
+ ),
+ 'launch' => array(
+ array(
+ 'label' => __( 'Hosting', 'ls-theme' ),
+ 'description' => __( 'Managed environments that match the platform, the workflows and the support model around it.', 'ls-theme' ),
+ 'url' => '/services/hosting/',
+ 'icon' => 'cloud',
+ ),
+ array(
+ 'label' => __( 'Performance', 'ls-theme' ),
+ 'description' => __( 'Core Web Vitals, caching, query review and template optimisation against real production data.', 'ls-theme' ),
+ 'url' => '/services/performance/',
+ 'icon' => 'gauge',
+ ),
+ array(
+ 'label' => __( 'Security', 'ls-theme' ),
+ 'description' => __( 'Audits, hardening guidance, monitoring and recovery planning that reduces risk before incidents.', 'ls-theme' ),
+ 'url' => '/services/security/',
+ 'icon' => 'shield',
+ ),
+ array(
+ 'label' => __( 'Training', 'ls-theme' ),
+ 'description' => __( 'Role-specific training and reference materials that move teams from dependency to confidence.', 'ls-theme' ),
+ 'url' => '/services/training/',
+ 'icon' => 'graduation-cap',
+ ),
+ ),
+ 'grow' => array(
+ array(
+ 'label' => __( 'Support', 'ls-theme' ),
+ 'description' => __( 'Maintenance, incident response and quiet improvement so platforms keep getting easier to run.', 'ls-theme' ),
+ 'url' => '/services/support/',
+ 'icon' => 'lifebuoy',
+ ),
+ array(
+ 'label' => __( 'SEO', 'ls-theme' ),
+ 'description' => __( 'Technical SEO, internal linking, schema and the publishing discipline that supports visibility.', 'ls-theme' ),
+ 'url' => '/services/seo/',
+ 'icon' => 'chart-line-up',
+ ),
+ array(
+ 'label' => __( 'Accessibility', 'ls-theme' ),
+ 'description' => __( 'Audits, remediation and the semantic structure that helps WCAG 2.2 AA stick over time.', 'ls-theme' ),
+ 'url' => '/services/accessibility/',
+ 'icon' => 'wheelchair',
+ ),
+ array(
+ 'label' => __( 'Email marketing', 'ls-theme' ),
+ 'description' => __( 'Journey planning, consent flows and the connection between email and the WordPress platform behind it.', 'ls-theme' ),
+ 'url' => '/services/email-marketing/',
+ 'icon' => 'envelope',
+ ),
+ ),
+ 'evolve' => array(
+ array(
+ 'label' => __( 'AI', 'ls-theme' ),
+ 'description' => __( 'AI-readiness reviews, governance and workflow planning — practical use without messy adoption.', 'ls-theme' ),
+ 'url' => '/services/ai/',
+ 'icon' => 'special-interests',
+ ),
+ ),
+);
+
+$ls_current_phase_slug = '';
+$ls_services_queried_obj = get_queried_object();
+if ( $ls_services_queried_obj instanceof WP_Post ) {
+ $ls_current_phase_slug = $ls_services_queried_obj->post_name;
+}
+
+$ls_phase_labels = array(
+ 'discover' => __( 'Discover', 'ls-theme' ),
+ 'create' => __( 'Create', 'ls-theme' ),
+ 'build' => __( 'Build', 'ls-theme' ),
+ 'launch' => __( 'Launch', 'ls-theme' ),
+ 'grow' => __( 'Grow', 'ls-theme' ),
+ 'evolve' => __( 'Evolve', 'ls-theme' ),
+);
+
+$ls_active_phase_label = isset( $ls_phase_labels[ $ls_current_phase_slug ] ) ? $ls_phase_labels[ $ls_current_phase_slug ] : __( 'Discover', 'ls-theme' );
+$ls_active_services = isset( $ls_phase_services_by_phase[ $ls_current_phase_slug ] ) ? $ls_phase_services_by_phase[ $ls_current_phase_slug ] : $ls_phase_services_by_phase['discover'];
+$ls_service_rows = array_chunk( $ls_active_services, 4 );
+$ls_active_phase_slug = isset( $ls_phase_services_by_phase[ $ls_current_phase_slug ] ) ? $ls_current_phase_slug : 'discover';
+$ls_phase_accent = 'var(--wp--custom--color--phase--' . $ls_active_phase_slug . ')';
+?>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ $ls_row ) : ?>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+