Replies: 2 comments 4 replies
-
|
I am coming to this with the mindset of what has come up over the past few weeks as common themes.
Now, in order to answer your questions:
I think we respond to the needs outlined above, people have been clearly asking for things and we start there.
This is a harder question. I almost at this point want a plugin and project repo seperate. My concern and I am going to state it is that this repo becomes a beautiful collection point for everything and confusing as a result. To me it would be clearer just as the experiments. Then having another one that is for the team and has other materials and collaboration issues, project management - that feels better. I say this as also someone that has wondered and stopped myself making an issue on here feeling it might be noisy. Ideally we want this to be a space people come to make bug reports on the experiments eventually also and/or enhancements as they are released. It feels confusing to have project issues also. Now, that’s not specifically the question you are asking me but it plays a little into the need to keep this as a plugin and related features. It should have consideration what goes here and not become a kitchen sink.
We have a range of options and I think this is where we activate other teams. I would say ‘all the places we can’, but having a central place to hold and form is useful. We need to be sure of the message and updating resources. WP Credits can also be a space for us to feed into as that project grows hopefully.
Again to me it’s all of those. The more we can, by having a central space to form our approach. This to me is a good old fashioned product launch.
We do it now. |
Beta Was this translation helpful? Give feedback.
-
|
Hey! After our 11/11 workshop I have lots of feedback. BackgroundWe worked with students aged 16 to 19, and had four mentors. Both mentors and students had a mix of technical experience. We focused on workforce development. Students were asked about their career goals. They used WordPress.com/AI to build their website that exemplified what they were doing and where they saw themselves in 10 years. After a quick chat talking about failures of the minimum wage and why students should prepare for the future, we got into the basics of LLMs. Tokenization, prompting, and vibe coding were quickly overviewed. Then students were asked to create their first prompt. We went over a few iterations of the first prompt, then students were given a WP.com user and let loose. ExpectationsLovable and Base44 are the two services experienced students knew most, but most students haven't vibe coded. It's important to state that "vibe coding" is a term that interested students most. I hope the WordPress team leans into that. PracticeMost students seemed impressed with an initial output from WP.com/AI. Difficulty came in updating sites. We gave a tertiary overview of the block editor, but wanted students to engage with chat-based WordPress management. This, to say the least, was lacking. The chat-based experience deleted large numbers of blocks unexpectedly or changed theme settings without knowing. Students were confused if they should edit via the block editor or the chat-based experience. Most students opted to abandon the chat-based experience. We may want to consider restricting a chat-based editor after a page is created. The chat based editor is great for putting ideas down on a page. It's terrible for editing them. After about an hour of fiddling and asking some questions to mentors, students seemed comfortable with WordPress and understood the limitations of the chat based experience. Four out of 22 students wanted to continue to engage WordPress, asking to have the sites transferred to their email. PedagogyI was really hoping to have the abilities plug in working. It would have been super helpful to show the students what the chat-based experience could and couldn't do. I'm sure that will set students' minds off. I also can't wait till we can have local copies of WordPress running on our daylight devices. The biggest administration headache for me was dealing with WP.com. We had multiple issues around credentialing and many students kept getting blocked by upgrade ads. In the future I plan on installing WP locally on every device and giving a quick workflow for student to publish it to WP.com or a cloud-based install that we set up. I'm also starting to see a clear path to a 201 version. I would like to start with chat based experiences, move to abilities and advanced WordPress administration, then get into contributing and coding - hopefully using agenic tools. Next StepsOur team has another workshop next month, and we were asked to do several more. The state of Louisiana is in fact hoping to arrange a traveling Vibe Coding workshop we do for businesses and students. They have commissioned a set decorator to build a traveling set for this, wonderfully enough. I will continue to base all of our work in WordPress and report back here. Video on the experience coming soon. But here are some cool photos: |
Beta Was this translation helpful? Give feedback.
-
|
This is all amazing feedback and fantastic work you're doing here @bbertucc! Thanks for taking to time to recap here as its super helpful signal to the non-technical userbase that's 50% of the intended audience of the AI Experiments plugin. Its worth noting that the wp.com/ai experience (powered by Automattic the company) is separate from the efforts of the WordPress.ORG AI team (powered by community member contributions), though there are likely some folks working on both efforts. |
Beta Was this translation helpful? Give feedback.
-
|
This is so great! Thank you for doing this and sharing such great feedback! I've passed this along internally to folks working in this within wp.com. 😄 |
Beta Was this translation helpful? Give feedback.
-
|
@jeffpaul we used the WP.com service because the experiments plug in wasn't quite ready for Showtime. I hope that Future workshops can use the .org plugin. We also requested sponsorship, so I can devote team members to directly contributing to the .org plugin. Our goal is to be as an open source as possible. |
Beta Was this translation helpful? Give feedback.
-
|
@bbertucc I am in awe of this. Thank you for such a recap and all the work. I hope sponsorship comes because seeing the potential of those people there fills my soul. Seeing them do this on forward thinking calm devices also made me happy. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As part of the broader WordPress AI work, we want to ensure that our communication and education reaches site owners and WordPress users who may not have a technical background. This is especially important as we get closer to the release of WordPress 6.9, where some of these AI features will become available for public testing primarily via the AI Experiments plugin but also via the other constituent AI Building Blocks (Abilities API, MCP Adapter, PHP+WP AI Client SDK).
The challenge: much of our current work is focused on design, development, and infrastructure. But we need to think ahead about how to present this in an approachable, useful way for those who primarily use WordPress to publish and manage content, rather than build plugins or write code. Said differently, this is a very technical topic, but one that non-technical users are interested and excited about so we need to ensure we're targeting and reaching out to them in ways that they'll understand.
A few starting questions:
I would love community input on:
By opening this discussion now, I hope to avoid a scramble in November or December and instead start preparing early to support the full range of WordPress users in understanding and benefiting from the AI work.
Beta Was this translation helpful? Give feedback.
All reactions