PADI / WebImplementation / Managed
Sprint 2 Summary Report
A concise delivery readout for the sprint completed from 14 June to 28 June 2026, based on live Jira sprint data.
Delivered
41
stories completed
Velocity
—
story points are not tracked on this board
Next sprint planning
0
Sprint 3 stories currently visible in Jira
Executive summary
Sprint 2 shows broad delivery across Drupal backend foundations, migration work, workflow configuration, JSON:API enablement, frontend integration, translation/Crowdin exploration, and CI quality improvements. The work materially advanced the core platform path: content model readiness, migration pipelines, editorial workflow, domain access evaluation, and Next.js rendering foundations.
The main open thread is the paragraph-to-frontend rendering and preview path. Several related POCs remain open or in progress, so the next delivery focus should be converting those learnings into a stable implementation plan and acceptance path.
Delivery highlights
- Completed the setup and configuration work for user roles, permissions, workflow notifications, notification templates, revision behavior, and additional workflow triggers.
- Moved migration work forward across users, media, taxonomies, articles and translations, videos, pages, posts, blog content, and Pros Blog content.
- Advanced API and frontend integration through JSON:API setup, field exposure, UI integration, draft preview exploration, and component configuration.
- Completed multiple domain access investigations, including Drupal Domain Access setup, taxonomy-versus-domain evaluation, and frontend filtering per domain.
- Improved engineering quality gates with CI updates for PHPStan and PHPUnit, plus Drupal core/module/theme updates.
Risks and carry-over
| Area | Status | Why it matters |
|---|---|---|
| Backend paragraph types + JSON:API + draft preview | In progress | Key dependency for predictable content rendering and editorial preview. |
| Frontend paragraph-to-React renderer, components, preview route | Open | Needed to turn backend paragraph structures into production-ready UI behavior. |
| Retire Layout Builder JSON code and hardcoded hero | Open | Reduces legacy/path divergence before the rendering approach hardens. |
| Storybook, Lighthouse a11y, Playwright e2e, cache tag verification | Open | Validation layer for quality, accessibility, regression safety, and caching. |
| Next.js 16 conventions and config improvements | Dev Test | Ensures the frontend remains aligned with the target framework baseline. |
Recommended next actions
- Finalize the paragraph rendering contract between Drupal JSON:API output and React components, including preview behavior.
- Prioritize the open frontend renderer and preview route work before adding more content/component scope.
- Close verification coverage for Storybook, Lighthouse accessibility, Playwright e2e, and cache tags so the new rendering path has measurable quality gates.
- Review Sprint 3 planning, since no next-sprint stories are currently visible in Jira.
Client/action board: PADI Jira board
Delivered this sprint
- Spike: Domain Access Module Setup and Multi-Domain Content Management
- Setup User Roles & Permissions
- Setup Content Workflow Notifications
- Pros Blog Migration: Wordpress to Drupal Migration, Part 1
- BE: Configure Workflow Notification Triggers
- Spike: JSON API Setup and Content Exposure
- POC: Setup Crowdin In-context Translations (JIPT)
- Configure User Roles and Permissions in Drupal
- Configure Notification Mechanism
- Email Notification Template Design and Build
- BE: Node ID and JSON API Module Setup
- BE: Users Migration
- BE: Media Migration
- BE: Taxonomies Migration
- BE: User Roles Migration
- BE: Article Content and Translations Migration
- BE: Node ID and JSON API Module Setup
- FE: JSON API Integration in UI
- Blog Migration: blog.padi.com to padi.com/blog, Part 2
- Translations Migration
- Pages Migration
- BE: Videos Migration
- Paragraphs to JSON API to Next.js Rendering and Draft Preview
- Spike: Paragraph Type to Component Contract as Single Source of Truth
- Spike: FE De-risking / POCs
- Content Workflow Email Notification Opt-Out for Individual Users
- Copy - Configure Workflow Transitions
- Copy - Configure Revision History and Rollback
- Copy - BE: HTTP Authentication Shield Setup
- Copy - BE: Configure Content Types for Translation and Crowdin TMGMT Integration
- Copy - Document AWS Cognito Authentication Architecture
- BE: JSON API Field Exposure and Component Configuration
- Domain Access Module POC
- BE: Taxonomy vs Domain Access — Evaluation and Recommendation
- FE: Content Filtering per Domain POC
- Revisions: workflow state reverting with content revert
- CI updates to run PHPStan for tests and add PHPUnit test step
- POC: CI/CD setup with Crowdin Translations
- Post Revisions Migration
- Drupal Core, Module and Theme Updates
- Configure Additional Workflow Notification Triggers