Profiles

Created issue #167 in the WordPress/secure-custom-fields repository:
Support for External Data Sources

Created issue #166 in the WordPress/secure-custom-fields repository:
Expose Custom Fields as a source for inline tokens

Created issue #165 in the WordPress/secure-custom-fields repository:
Redesign the export-import workflow UX

Created issue #164 in the WordPress/secure-custom-fields repository:
Integrate file-based definitions with WordPress Blueprints

Created issue #163 in the WordPress/secure-custom-fields repository:
Implement alternative, unified file-based definitions

Created issue #162 in the WordPress/secure-custom-fields repository:
Create Schemas for the current implementation of file-based definitions

Created issue #161 in the WordPress/secure-custom-fields repository:
Overhauling the file-based content modeling

Created issue #160 in the WordPress/secure-custom-fields repository:
Create a Playground site that can serve as interactive documentation

Created issue #159 in the WordPress/secure-custom-fields repository:
Audit the current documentation for missing gaps and opportunities

Created issue #158 in the WordPress/secure-custom-fields repository:
Documentation revamp

Created issue #157 in the WordPress/secure-custom-fields repository:
SCF Roadmap

Created issue #156 in the WordPress/secure-custom-fields repository:
Migrate the SCF post editing pages to leverage Core Components

Created issue #155 in the WordPress/secure-custom-fields repository:
Support Creating Taxonomies Within the Editor

Created issue #154 in the WordPress/secure-custom-fields repository:
Support Custom Field Editing in Editor Sidebar

Merged pull request #141 into WordPress/secure-custom-fields:
Bump http-proxy-middleware from 2.0.7 to 2.0.9

Created issue #153 in the WordPress/secure-custom-fields repository:
Automatic changelog generation

Created issue #152 in the WordPress/secure-custom-fields repository:
Release management: classify PRs in the right milestone to generate changelog

Created issue #151 in the WordPress/secure-custom-fields repository:
Release management: automatically tag `@since` annotations with the correct version

Created issue #150 in the WordPress/secure-custom-fields repository:
Migration of old APIs and filenames to SCF namespace

Closed issue #149 on the WordPress/secure-custom-fields repository:
Set up e2e testing environment

Created issue #149 in the WordPress/secure-custom-fields repository:
Set up e2e testing environment

Created issue #148 in the WordPress/secure-custom-fields repository:
DevOps and Code Quality tasks

Created issue #147 in the WordPress/secure-custom-fields repository:
Implement the Options Pages listing with DataViews

Created issue #146 in the WordPress/secure-custom-fields repository:
Implement the Taxonomies listing with DataViews

Created issue #145 in the WordPress/secure-custom-fields repository:
Implement the Post Types listing with DataViews

Created issue #144 in the WordPress/secure-custom-fields repository:
Implement the Field Group listing with DataViews

Created issue #143 in the WordPress/secure-custom-fields repository:
Implement CPT listings with DataViews

Created issue #142 in the WordPress/secure-custom-fields repository:
Migrate Admin Listing Pages (edit.php) to DataViews

Created issue #140 in the WordPress/secure-custom-fields repository:
Add Command Palette comands to navigation to options pages

Created issue #139 in the WordPress/secure-custom-fields repository:
Enable the Command Palette everywhere for logged-in users

Created issue #138 in the WordPress/secure-custom-fields repository:
Add Command Palette commands for user-defined CPTs

Created issue #137 in the WordPress/secure-custom-fields repository:
Add Command Palette commands for SCF data structures

Created issue #136 in the WordPress/secure-custom-fields repository:
Command Palette Integration

Merged pull request #99 into WordPress/secure-custom-fields:
Add composer installation to docs/welcome

Merged pull request #121 into WordPress/secure-custom-fields:
Add Command Palette support

Closed issue #6 on the WordPress/secure-custom-fields repository:
Version numbers from WPEngine's ACF plugin mixed into SCF plugin

Pull request #129 merged into WordPress/secure-custom-fields:
Specify the version refers to `SCF` in `@since` annotations

Submitted pull request #129 to WordPress/secure-custom-fields:
Specify the version refers to `SCF` in `@since` annotations

Submitted pull request #128 to WordPress/secure-custom-fields:
REST API: Add `source` parameter for types endpoint

Submitted pull request #121 to WordPress/secure-custom-fields:
Add Command Palette support

Pull request #118 merged into WordPress/secure-custom-fields:
Update initialization of the `acfL10n` object to ensure it's available globally

Submitted pull request #118 to WordPress/secure-custom-fields:
Update initialization of the `acfL10n` object to ensure it's available globally

Pull request #112 merged into WordPress/secure-custom-fields:
Upgrade the tested up to version to WordPress 6.8

Submitted pull request #112 to WordPress/secure-custom-fields:
Upgrade the tested up to version to WordPress 6.8

Pull request #82 merged into WordPress/secure-custom-fields:
Fixo typos in secure-custom-fields.php

Submitted pull request #82 to WordPress/secure-custom-fields:
Fixo typos in secure-custom-fields.php