1.6 KiB
Delta Spec: Landing render memory
ADDED Requirements
Requirement: Bound decorative render cost
The landing page MUST bound the amount of continuously animated decorative DOM/composited layers used for backgrounds.
Scenario: Animated background is present but constrained
Given the landing page renders decorative background effects When the page is idle Then background effects MUST NOT rely on large numbers of infinite particle/orb/shape/grid animations.
Requirement: Avoid duplicated hero background work
Sections MUST NOT duplicate the most expensive hero background variant when a lighter section treatment preserves the visual hierarchy.
Scenario: CTA renders after hero
Given the hero has already rendered the primary dynamic background
When the CTA section renders
Then it SHOULD use a lighter decorative treatment than DynamicBackground variant="hero".
Requirement: Reduce expensive blur and scroll compositing
The landing page SHOULD reduce oversized blur radii and scroll-linked transforms where they create large repaint/compositor surfaces without essential UX value.
Scenario: Visual depth is preserved
Given blur and motion effects are reduced When a user views hero, compliance, and CTA sections Then the page MUST retain the general gradient/depth aesthetic without excessive compositor memory pressure.
Requirement: Verify landing quality gate
The implementation MUST pass landing linting and MUST NOT require a production build for verification.
Scenario: Landing lint passes
Given changes are made under services/landing
When npm run lint runs in services/landing
Then it MUST complete successfully.