New Paragraph
New Paragraph

We’ve added new quick edit suggestions right into the AI Content Assistant dialog box, to allow you to shorten, lengthen, and improve text better and faster.
To give an example, if your suggested text is longer than expected, you can easily ask the Assistant to cut it short right here at the click of a button, without needing to re-select the text and open Assistant's text menu all over again.
An added bonus: these actions are also available when generating SEO meta tags for individual fields (only title or description).
We’ve added the option to quickly log in to other workspaces you might need to when working on multiple accounts.
Your Duda profile menu now includes the option to Change Workspace. Opting for this option will show you the available accounts, and clicking each of these will put you through the login to the other account.

We've added the ability to add inline binding to a page's head HTML. Until now you could connect a Dynamic Page's meta title and meta description to the site’s internal collection, to dynamically show metadata for each page item.
So what’s new? You can now add other metadata, and insert custom code to the Dynamic Page's head HTML. Another option that’s now possible is to connect Content Library fields to the <head> section of regular (non-Dynamic) site pages.

That's it for this month's Wrap Up. We hope you find these useful. Got an idea or a feature request? Stop by our Idea Board and post it.

We’ve added new quick edit suggestions right into the AI Content Assistant dialog box, to allow you to shorten, lengthen, and improve text better and faster.
To give an example, if your suggested text is longer than expected, you can easily ask the Assistant to cut it short right here at the click of a button, without needing to re-select the text and open Assistant's text menu all over again.
An added bonus: these actions are also available when generating SEO meta tags for individual fields (only title or description).
We’ve added the option to quickly log in to other workspaces you might need to when working on multiple accounts.
Your Duda profile menu now includes the option to Change Workspace. Opting for this option will show you the available accounts, and clicking each of these will put you through the login to the other account.

We've added the ability to add inline binding to a page's head HTML. Until now you could connect a Dynamic Page's meta title and meta description to the site’s internal collection, to dynamically show metadata for each page item.
So what’s new? You can now add other metadata, and insert custom code to the Dynamic Page's head HTML. Another option that’s now possible is to connect Content Library fields to the <head> section of regular (non-Dynamic) site pages.

That's it for this month's Wrap Up. We hope you find these useful. Got an idea or a feature request? Stop by our Idea Board and post it.
As part of our ongoing efforts to improve website experience, speed, and Core Web Vitals scores, Duda now has a set of servers that deliver Duda websites from servers based in Europe. By having a set of servers in the EU, we are able to have the first response time (also known as Time to First Byte, TTFB) faster for site visitors that are closer to the EU.
We silently rolled this out a few weeks ago and are already seeing a big decrease in loading times for visitors coming to sites from the EU.
This new European server also adds an additional layer of resiliency to the Duda platform. If the primary US data center goes down, all website traffic will be routed to the cached version in the EU until the US data center comes back online. This also works in reverse, if the European layer goes down, traffic will get routed to the US, too.
Duda has set up a new service that caches a version of the live web page in the European region. This takes our existing caching infrastructure and places it in Europe, in addition to the United States. We are then able to route traffic from site visitors coming to the website to either the US or EU data center automatically, based on which is closer.
Yes, this is true! It’s important to note that websites are delivered in two ways: There’s the primary HTML document that’s downloaded and then all the other assets within the website, like images, videos, javascript files, etc..
Before this European caching server, Duda only responded with the HTML from the United States. By delivering the primary page HTML from a closer server, we are able to speed up the all-important first render time of the website even more.
All other assets (images, videos, javascript files, etc..) are already on the global CDN and this is not changing.
It’s important to take a minute and make sure we’re clear on what this is and what this is not.
•

Sign up to get feature releases, tools, and more to your inbox.