You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bbertucc since that roadmap is a markdown file, it requires a commit to update the checklists. The best way to see real-time updates is the project board: WordPress AI Roadmap (view). Feel free to grab something from the To do column to work on as things there are in the near-term milestones. Happy to chat async or sync on any questions you or your team have on things already described as features/tasks/bugs or something additional y'all have in mind, just reach out... thanks!
What dev environment are you provisioning? Just running the plugin shows that composer needs to run, and contributing.md only mentions testing, not provisioning a dev environment.
I want to make sure my team is in sync with your environment.
What dev environment are you provisioning? Just running the plugin shows that composer needs to run, and contributing.md only mentions testing, not provisioning a dev environment.
Still early days here and so likely to change over time as actual functionality is added to the plugin (right now the plugin doesn't do much). But the main command you'll need to run is composer install. That should get you in a place where you can install and activate the plugin.
Soon we'll start having other assets (like JS and CSS files) and at that point you'll also need to run npm i && npm run build. You can run those commands now but the build command won't actually do anything yet as we don't have any files to build. If you're wanting to run tests locally though, you will need to at least run npm i to bring in those dependencies.
Activity
jeffpaul commentedon Oct 29, 2025
@bbertucc since that roadmap is a markdown file, it requires a commit to update the checklists. The best way to see real-time updates is the project board: WordPress AI Roadmap (view). Feel free to grab something from the
To docolumn to work on as things there are in the near-term milestones. Happy to chat async or sync on any questions you or your team have on things already described as features/tasks/bugs or something additional y'all have in mind, just reach out... thanks!bbertucc commentedon Oct 29, 2025
@jeffpaul I can't access that project. Maybe it's private? Anyway to add me? Getting with my team tomorrow to tackle To Dos.
jeffpaul commentedon Oct 29, 2025
@bbertucc bah, you're right, it was private. i've opened that up now, can you confirm?
bbertucc commentedon Oct 29, 2025
Yep! I see it @jeffpaul.
What dev environment are you provisioning? Just running the plugin shows that composer needs to run, and contributing.md only mentions testing, not provisioning a dev environment.
I want to make sure my team is in sync with your environment.
jeffpaul commentedon Oct 29, 2025
@dkotter mind answering that question above? I can get that into the contributing doc to improve our details there afterwards.
dkotter commentedon Oct 29, 2025
Still early days here and so likely to change over time as actual functionality is added to the plugin (right now the plugin doesn't do much). But the main command you'll need to run is
composer install. That should get you in a place where you can install and activate the plugin.Soon we'll start having other assets (like JS and CSS files) and at that point you'll also need to run
npm i && npm run build. You can run those commands now but the build command won't actually do anything yet as we don't have any files to build. If you're wanting to run tests locally though, you will need to at least runnpm ito bring in those dependencies.