-
-
Notifications
You must be signed in to change notification settings - Fork 2
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Define the performance measurement and value attribution contract
area: integrationsExternal scripts, analytics, CDN providers, APIs, or third-party services.External scripts, analytics, CDN providers, APIs, or third-party services.area: performancePerformance-sensitive behavior, page weight, caching, preloading, or resource hints.Performance-sensitive behavior, page weight, caching, preloading, or resource hints.enhancementFeature or improvement request that changes product behavior or user experience.Feature or improvement request that changes product behavior or user experience.priority: highImportant for the next planned release or high user impact.Important for the next planned release or high user impact.status: needs-specNeeds acceptance criteria, scope, UX, or technical design before implementation.Needs acceptance criteria, scope, UX, or technical design before implementation.Status: Open.Add an evidence-based Query Loop configuration audit
area: compatibilityWordPress, PHP, multisite, WooCommerce, theme, or plugin compatibility.WordPress, PHP, multisite, WooCommerce, theme, or plugin compatibility.area: performancePerformance-sensitive behavior, page weight, caching, preloading, or resource hints.Performance-sensitive behavior, page weight, caching, preloading, or resource hints.enhancementFeature or improvement request that changes product behavior or user experience.Feature or improvement request that changes product behavior or user experience.priority: mediumUseful or user-impacting work that should be planned but is not blocking now.Useful or user-impacting work that should be planned but is not blocking now.status: needs-specNeeds acceptance criteria, scope, UX, or technical design before implementation.Needs acceptance criteria, scope, UX, or technical design before implementation.Status: Open.Define a local site baseline inventory for performance guidance
area: admin-uiWordPress admin screens, settings UI, notices, onboarding, or admin bar UX.WordPress admin screens, settings UI, notices, onboarding, or admin bar UX.area: performancePerformance-sensitive behavior, page weight, caching, preloading, or resource hints.Performance-sensitive behavior, page weight, caching, preloading, or resource hints.enhancementFeature or improvement request that changes product behavior or user experience.Feature or improvement request that changes product behavior or user experience.priority: highImportant for the next planned release or high user impact.Important for the next planned release or high user impact.status: needs-specNeeds acceptance criteria, scope, UX, or technical design before implementation.Needs acceptance criteria, scope, UX, or technical design before implementation.Status: Open.Continuously verify Perform's documented PHP 7.4 support floor
area: build-ciComposer, npm, linting, static analysis, GitHub Actions, or release automation.Composer, npm, linting, static analysis, GitHub Actions, or release automation.area: compatibilityWordPress, PHP, multisite, WooCommerce, theme, or plugin compatibility.WordPress, PHP, multisite, WooCommerce, theme, or plugin compatibility.owner:codexReady for Codex/orchestrator/worker action.Ready for Codex/orchestrator/worker action.priority: highImportant for the next planned release or high user impact.Important for the next planned release or high user impact.risk: backward-compatibilityTouches public data, options, hooks, migrations, or established behavior.Touches public data, options, hooks, migrations, or established behavior.status: readyScoped enough for implementation without major open questions.Scoped enough for implementation without major open questions.type: maintenanceEngineering maintenance, CI, dependency, refactor, tooling, or release hygiene.Engineering maintenance, CI, dependency, refactor, tooling, or release hygiene.Status: Open.#205 In performwp/perform;Make settings feedback, Asset Manager, and cache observability accessible
area: admin-uiWordPress admin screens, settings UI, notices, onboarding, or admin bar UX.WordPress admin screens, settings UI, notices, onboarding, or admin bar UX.area: assets-managerAsset Manager behavior, compatibility, UI, persistence, or per-page controls.Asset Manager behavior, compatibility, UI, persistence, or per-page controls.enhancementFeature or improvement request that changes product behavior or user experience.Feature or improvement request that changes product behavior or user experience.owner:codexReady for Codex/orchestrator/worker action.Ready for Codex/orchestrator/worker action.priority: mediumUseful or user-impacting work that should be planned but is not blocking now.Useful or user-impacting work that should be planned but is not blocking now.status: readyScoped enough for implementation without major open questions.Scoped enough for implementation without major open questions.Status: Open.#204 In performwp/perform;Retire the obsolete classic settings renderer and duplicate save path
area: admin-uiWordPress admin screens, settings UI, notices, onboarding, or admin bar UX.WordPress admin screens, settings UI, notices, onboarding, or admin bar UX.area: settingsSettings schema, storage contracts, migration, import/export, and validation.Settings schema, storage contracts, migration, import/export, and validation.owner:codexReady for Codex/orchestrator/worker action.Ready for Codex/orchestrator/worker action.priority: mediumUseful or user-impacting work that should be planned but is not blocking now.Useful or user-impacting work that should be planned but is not blocking now.risk: backward-compatibilityTouches public data, options, hooks, migrations, or established behavior.Touches public data, options, hooks, migrations, or established behavior.status: readyScoped enough for implementation without major open questions.Scoped enough for implementation without major open questions.type: maintenanceEngineering maintenance, CI, dependency, refactor, tooling, or release hygiene.Engineering maintenance, CI, dependency, refactor, tooling, or release hygiene.Status: Open.#203 In performwp/perform;Make the settings AJAX endpoint a strict schema boundary
area: settingsSettings schema, storage contracts, migration, import/export, and validation.Settings schema, storage contracts, migration, import/export, and validation.bugConfirmed or likely defect affecting runtime behavior, UX, compatibility, or data handling.Confirmed or likely defect affecting runtime behavior, UX, compatibility, or data handling.owner:codexReady for Codex/orchestrator/worker action.Ready for Codex/orchestrator/worker action.priority: mediumUseful or user-impacting work that should be planned but is not blocking now.Useful or user-impacting work that should be planned but is not blocking now.risk: backward-compatibilityTouches public data, options, hooks, migrations, or established behavior.Touches public data, options, hooks, migrations, or established behavior.status: readyScoped enough for implementation without major open questions.Scoped enough for implementation without major open questions.Status: Open.#202 In performwp/perform;Preserve unsaved React settings edits across save notifications
area: admin-uiWordPress admin screens, settings UI, notices, onboarding, or admin bar UX.WordPress admin screens, settings UI, notices, onboarding, or admin bar UX.area: settingsSettings schema, storage contracts, migration, import/export, and validation.Settings schema, storage contracts, migration, import/export, and validation.bugConfirmed or likely defect affecting runtime behavior, UX, compatibility, or data handling.Confirmed or likely defect affecting runtime behavior, UX, compatibility, or data handling.owner:codexReady for Codex/orchestrator/worker action.Ready for Codex/orchestrator/worker action.priority: highImportant for the next planned release or high user impact.Important for the next planned release or high user impact.status: readyScoped enough for implementation without major open questions.Scoped enough for implementation without major open questions.Status: Open.#201 In performwp/perform;Fix full-page cache handling for HTTP HEAD requests
area: cachePage cache, menu cache, preload, invalidation, observability, or cache settings.Page cache, menu cache, preload, invalidation, observability, or cache settings.area: frontendPublic-facing frontend output, assets, feeds, headers, or visitor behavior.Public-facing frontend output, assets, feeds, headers, or visitor behavior.area: performancePerformance-sensitive behavior, page weight, caching, preloading, or resource hints.Performance-sensitive behavior, page weight, caching, preloading, or resource hints.bugConfirmed or likely defect affecting runtime behavior, UX, compatibility, or data handling.Confirmed or likely defect affecting runtime behavior, UX, compatibility, or data handling.owner:codexReady for Codex/orchestrator/worker action.Ready for Codex/orchestrator/worker action.priority: highImportant for the next planned release or high user impact.Important for the next planned release or high user impact.status: readyScoped enough for implementation without major open questions.Scoped enough for implementation without major open questions.Status: Open.#200 In performwp/perform;Refresh PerformWP site content around 1.6.0 positioning and conversion paths
area: docsDocumentation URLs, help links, readme copy, changelog, or support guidance.Documentation URLs, help links, readme copy, changelog, or support guidance.area: frontendPublic-facing frontend output, assets, feeds, headers, or visitor behavior.Public-facing frontend output, assets, feeds, headers, or visitor behavior.enhancementFeature or improvement request that changes product behavior or user experience.Feature or improvement request that changes product behavior or user experience.priority: mediumUseful or user-impacting work that should be planned but is not blocking now.Useful or user-impacting work that should be planned but is not blocking now.status: needs-specNeeds acceptance criteria, scope, UX, or technical design before implementation.Needs acceptance criteria, scope, UX, or technical design before implementation.Status: Open.Add public PerformWP site scan workflow for growth and education
area: frontendPublic-facing frontend output, assets, feeds, headers, or visitor behavior.Public-facing frontend output, assets, feeds, headers, or visitor behavior.area: integrationsExternal scripts, analytics, CDN providers, APIs, or third-party services.External scripts, analytics, CDN providers, APIs, or third-party services.area: performancePerformance-sensitive behavior, page weight, caching, preloading, or resource hints.Performance-sensitive behavior, page weight, caching, preloading, or resource hints.enhancementFeature or improvement request that changes product behavior or user experience.Feature or improvement request that changes product behavior or user experience.priority: mediumUseful or user-impacting work that should be planned but is not blocking now.Useful or user-impacting work that should be planned but is not blocking now.status: needs-specNeeds acceptance criteria, scope, UX, or technical design before implementation.Needs acceptance criteria, scope, UX, or technical design before implementation.Status: Open.Research local slow query analysis and EXPLAIN-based guidance
area: compatibilityWordPress, PHP, multisite, WooCommerce, theme, or plugin compatibility.WordPress, PHP, multisite, WooCommerce, theme, or plugin compatibility.area: performancePerformance-sensitive behavior, page weight, caching, preloading, or resource hints.Performance-sensitive behavior, page weight, caching, preloading, or resource hints.enhancementFeature or improvement request that changes product behavior or user experience.Feature or improvement request that changes product behavior or user experience.priority: mediumUseful or user-impacting work that should be planned but is not blocking now.Useful or user-impacting work that should be planned but is not blocking now.risk: backward-compatibilityTouches public data, options, hooks, migrations, or established behavior.Touches public data, options, hooks, migrations, or established behavior.status: needs-specNeeds acceptance criteria, scope, UX, or technical design before implementation.Needs acceptance criteria, scope, UX, or technical design before implementation.Status: Open.