Goodbye notice

Date: October 12th, 2024

I am officially terminating my core contributions and involvement with the WordPress project. This project was something I poured hundreds of hours into and it greatly pains me to just stop here.

Anyone is free to lead the project again in the #core-fields channel of Slack. I am done making excuses for Matt's actions and will not associate myself with core any longer.

The content below represents the latest revision of the readme as it was prior to me leaving.

Yours previously fully,

Scott Kingsley Clark

WordPress Fields API (2024)

Please note: We are currently in the research phase of this project.

The Fields API project aims to provide a unified PHP API to work with any screen that has a form on it within the WordPress admin area.

Previous iterations

• Fields API proposal for WordPress Core (2023)
• Fields API proposal for WordPress Core (2015-2017)
• The old WP Metadata API / UI repository
• Related: A proof of concept Administration UI for the WP Fields API (2016)

Current Contributors

• Scott Kingsley Clark - @sc0ttkclark (.org profile)
  • Senior Software Engineer at Pagely / GoDaddy
  • Lead Developer of the Pods Framework
  • Previously Co-Lead of the Fields API project from 2013-2016 and then Lead Developer since 2016
• Cory Hughart - @cr0ybot (.org profile)
  • Senior Web Dev at Alpha Particle
• Ryan Neudorf - @ohryan (.org profile)
  • Senior Software Engineer at GoDaddy (Managed WooCommerce)

Past Contributors

If your listing here needs to be adjusted, feel free to PR it to associate your work with sponsored time or add other details like your .org profile link.

• Alex Standiford - @alexstandiford (.org profile)
  • WordPress Plugin Developer
• Laurie Wood - (.org profile)
  • Chief Product Officer at Arena
• Timothy Wood - @codearachnid (.org profile)
  • Co-Founder, Chief Solutions Architect at Always Curious
• Willington Vega - @wvega (.org profile)
  • Senior Software Engineer at GoDaddy
• Joe Dolson - @joedolson (.org profile)
  • WP Core Committer
  • Working on the Accessibility team
  • Sponsored by GoDaddy for WP contributions
• Eric Andrew Lewis - @ericandrewlewis (.org profile)
  • Software Engineer at Google
  • Previously Co-Lead of the Fields API project from 2013-2016 with @sc0ttkclark (.org profile)
• 10up Sponsored Time - @10up (.org profile)
  • Contributor: Scott Kingsley Clark (2014-2016) - @sc0ttkclark
  • Contributor: Aaron Brazell (2014) - @technosailor
  • Contributor: Taylor Lovett (2014) - @tlovett1
• WebDevStudios Sponsored Time - @webdevstudios (.org profile)
  • Contributor: Scott Kingsley Clark (2013-2014) - @sc0ttkclark
• Felix Arntz - @felixarntz
• Tom Auger - @Zeitguys
• Daniel Bachhuber - @danielbachhuber
• Ramon van Belzen - @Ramoonus
• Christian Leucht - @Chrico
• Yoni Mazuz - @ymazuz
• Manuel Schmalstieg - @ms-studio
• Dan - Lucian Ștefancu - @danstefancu

Other Collaborators

We enjoy the benefits of having other collaborators involved with Fields API who have helped provide additional context with their own experiences and projects. They deserve credit for helping restart the Fields API project in 2023 to it's current form.

• Matthew Batchelder - @borkweb (.org profile)
  • Director of Engineering at StellarWP
• Jason Adams - @JasonTheAdams (.org profile)
  • Manager of Development at GiveWP
• Peter Ingersoll - @peteringersoll (.org profile)
  • Digital Marketing Consultant and Producer at Ingersoll Interactive

More Information

You can find out more about the project's history by looking over the #fields-api tag on Make WordPress Core blog:

#fields-api