November Release · Confidence & Recommendations PADI Web Modernization · 28 August 2026

November release confidence & recommendations

12 of 13 at high confidence
High confidence
12 epics
Medium confidence
1 epic
Low confidence
None
Dependencies confirmed by
4 September 2026
01

Position at a glance

Twelve of the thirteen tracked epics are at high confidence for the November release. The remaining epic carries medium confidence, because design input is still being settled rather than because of delivery capacity. No epic now sits at low confidence.

Four epics are progressing against defined dependencies on the PADI engineering and design teams. These are set out in section 03, with the associated dates in section 05. Each dependency is scheduled, and none currently places the November date at risk.

Confirmation of the items listed in section 05 during the first week of September holds the position described here.

02

Confidence by epic

Epic / featureConfidenceDependency
Progressing without external dependency
Experience First HomepageHighIn progress. No blockers or dependencies.
Global Navigation & Site IAHighIn progress. No blockers or dependencies.
Editorial roles & content workflowHighIn progress. No blockers or dependencies.
AmbassadiversHighIn progress. No blockers or dependencies.
Consumer Blogs migration and consolidationHighIn progress. No blockers or dependencies.
Pros Blog consolidation and migrationHighIn progress. No blockers or dependencies.
Regional consolidation & localisationHighIn progress. No blockers or dependencies.
Configurable templates / pagesHighIn progress. No blockers or dependencies.
DAM integrationHighIn progress. No blockers or dependencies.
Progressing against defined dependencies
Device fingerprinting High Dependent on the PADI engineering team providing the endpoint and confirming that the supporting data store is ready.
MyPADI — unified diver profile and preferences, account creation & login, logged-in experience High Dependent on the final persona set being confirmed and on the PADI engineering team identifying the final set of APIs. Assumes all requirements are served by existing APIs.
Search High November scope confirmed as Drupal database search, which is within our own delivery control. Selection of the target-state search platform continues on a separate track.
Unified Locator Medium Dependent on designs being finalised in the first week of September. Implemented against its own search index rather than global site search. Natural language query is outside November scope.
03

Dependencies and conditions

High Device fingerprinting
Dependency
The PADI engineering team to provide the endpoint and confirm that the supporting data store is ready to receive data.
Condition
With the endpoint available and the data store in place, delivery sits comfortably within the November window.
High MyPADI — unified diver profile, account creation & logged-in experience
Dependency
The final set of personas to be confirmed, and the PADI engineering team to identify the final set of APIs to be consumed.
Condition
The November position assumes that all requirements can be served by existing APIs. Should a requirement need a new API, that item would be reassessed against the release date.
High Search
Dependency
None for November. The intermediate capability is built within our own delivery control. Selection of the target-state search platform remains open but is no longer on the November critical path.
Condition
November delivers an intermediate capability built on Drupal database search. Its feature set is narrower than a dedicated search platform, but the resulting experience is comparable to search on padi.com today.
Option
Should PADI wish to bring the target-state platform forward, Axelerant can hold the year-one licence, with the subscription transferring to PADI from year two.
Medium Unified Locator
Dependency
Designs to be finalised in the first week of September.
Condition
On that basis, Unified Locator is held within the November release. It is implemented against its own dedicated search, scoped to locator content, rather than through global site search. Natural language search queries are outside November scope and would follow once the target-state search platform is in place.
04

Recommendation

Recommended

Proceed with the November scope as set out above, delivering an intermediate Drupal database search and holding Unified Locator in the release.

This keeps all thirteen epics within November. Because the intermediate search experience is comparable to search on padi.com today, the selection of the target-state platform can be concluded on its own timeline rather than against the release date. Unified Locator is delivered against its own dedicated search and is therefore unaffected by that selection. Natural language query is excluded from November and would be scheduled alongside the target-state platform.

05

Dependency dates

  1. First week of September — Unified Locator designs finalised.
  2. 4 September — Final MyPADI persona set confirmed.
  3. 4 September — PADI engineering to confirm the final MyPADI API set, and that all requirements are served by existing APIs.
  4. 4 September — PADI engineering to confirm the device fingerprinting endpoint and data store readiness.
  5. Separate track — Target-state search platform selection. No November dependency.
06

Daily tracker

Updated daily
Progress against every epic above, day by day.
PADI_Delivery_Calendar_Tracker ↗