‘wordpress adjacent’ should be more precise

There are lot of us who are still involved with WordPress and who building tools and or solutions that may not only interact with WordPress or that start with WordPress and fan out from there..   Imagine thinking you're going to hear someone talk about building headless applications WordPress and all that comes with that only to hear that engineer is going to be talking about building utility that incorporates Google Cloud Functions and custom endpoints to send data to database and to WordPress database, too..   Starting more broadly, I would say, at it's core, being WordPress adjacent refers to individuals or projects associated with WordPress, either through direct use or integration with technologies related to the core application..   Here's why I say that In their mind, people already have what it means to be WordPress adjacent.   The imprecision of WordPress adjacent is both blessing and curse.   Imagine trying to explain your job to someone using this term chances are, you'd end up providing explanation that leaves the them more confused than not..   Further, I'm grateful for it integrating them, and then having them still communicate with WordPress..   From developing custom APIs that communicate with WordPress installations to creating data systems all of.   Whether it's through developing plugins, creating bespoke themes, enhancing user experience, building headless front-ends, communicating with third-party APIs and integrating them back into WordPress application, and so on...   For those of us who work in this space, we have responsibility to those.   Read more