AI is coming to Elements

Hey Weavers,

You may have noticed that Elements releases have been arriving a little slower than usual recently. That’s because we’ve been hard at work on some much bigger features behind the scenes, and today I want to talk about one of them: AI in Elements.

I’m excited to share that we’ve been researching and developing AI features for Elements for many months now. It’s been a challenging journey, with plenty of twists and turns along the way, but the progress we’ve made recently has been incredibly encouraging.

Our early experiments with AI showed promise, but the results weren’t quite where we wanted them to be. Everything changed when we started building dedicated tools inside Elements that AI can interact with. I won’t go into the technical details just yet, as that’s part of our secret sauce, but those tools have allowed us to achieve results that have genuinely exceeded our expectations.

Today, we’re ready to start sharing that journey with you.

This video is our first look at Elements AI and a small glimpse of what’s coming next. Over the coming weeks and months, we’ll be publishing regular development updates, showing you what we’re building, what we’re learning, and how AI is being thoughtfully integrated into Elements.

Watch the video below for an early teaser…

Remember this is just the beginning, we’ll be back next week with another update you won’t want to miss!

Please reply below and let us know what AI features you’d like to see inside of Elements.

Impressive!

Very ironic that this very question came up today on the board.

I’m hoping you are going to be making money from an affiliate link to Claude subscriptions after teasing this:-)

Amazing integration. Well done!

Absolutely amazing and can’t wait for more!

I think it would be helpful to be able to generate page layouts either from existing Menu Structures, Banners, and Footers or create them from scratch make them global and use them to make a new page. You could also have it add components to the new pages.

If you’re someone who likes to be able to speak to the Ai and then they do what you ask this could save a lot of key strokes and mouse dragging.

Does the built-in AI support Polish, so I can prompt in my native language, or only English and a few other popular languages? This will be the key feature that determines whether to stick with Elements or use other tools.

Regards Ryszard

The final version will be built into Elements, so you won’t have to use Claude.

Yes, it should support any language the AI service we use on the backend supports. We’ll obviously need to test and confirm during development.

Yup, that sure would be handy!

Even better, great work Dan

I already had a feeling that something was going on … but the fact that it turns out to be AI is still a surprise. I had actually hoped the CMS would be finalized first.

That said, the obvious question is: which AI agents will this be built for?

I only cancelled my ChatGPT subscription today and switched to Claude — just to realize that Claude really isn’t for me, or at least not for the way I work. So it looks like I’ll probably be sticking with ChatGPT after all.

Long story short, here’s the question:

Claude?
ChatGPT?

We can work on more than one thing at once :wink: what exactly do you need finalised?

As this is still in-development, I can’t give you a definitive answer yet. However we’re building this into Elements, so users won’t need to worry about which AI service they should be using. It’ll just work, no fiddly setup or connection required, just like how our AI-writing assistant works. We think this is the best approach for the majority of our users.

So does that mean we are going to have to have a separate subscription for Elements AI.

If so, it would be good to be able to leverage my existing Claude subscription without paying for another.

That will be perfect to make a site more accessible and google friendly. Check and fix hierarchies, check and fix contrast issues, add alt texts, add the correct attributes like aside or article, etc. @dan

Love, love, love what I’m seeing here. The only thing that raised a red flag for me was a reply to a YouTube comment where @dan mentioned they’ll be building this into Elements. I’d love for them to elaborate on what that means. If it’s going to function like the current AI features in Elements, I’d have to push back on that — not because those features don’t work well, but because we’re limited by the credits Elements allocates us. Most of us are already paying for our own AI subscriptions, so locking this behind Elements’ ecosystem would be a real disappointment. I think the direction you demonstrated in the video is exactly the right approach.

I agree. I pay monthly for perplexity and would like to use this for elements as well.

The only thing - all that programming isn’t free… they have to do a lot of work to make it work with AI

A lot of programming…

I don’t see how you can do that for free…

You want the features - then compensation- my guess - will be required…

How can you run a business for free???

They are spending tons of man hours developing and implementing it - imho they have to charge

That’s why I pay them $250 a year for my Elements License

Arlen - me too - but this is an add on service - this is not a stock software feature

This is a newly created set of features that are not needed for the software to function

If a customer came to your business and wanted you to work more for them and do more for them

Would you charge them? Or do it for free?

In my opinion, the whole point of Elements moving to a subscription-based pricing model was to fund continued development and improvement of the platform — that purpose is undermined if every add-on feature comes with an additional cost.