Connecting to External CMS

At a glance

The community members discuss the placement of data sources when connecting to the WordPress REST API or other external CMS. They suggest that data can be defined either close to where it is used, globally in the body, or on the root if it is needed on every page. Only global root and body variables can be accessed from page settings. The community members advise starting with pre-built integrations, such as the one for WordPress, and placing queries in the body for easier management, unless the data is needed on every page, in which case it should be placed on the root. They also note that the placement of the data source does not significantly affect performance.

rrsppl

I'm a beginner in this area, and I have a question. In YouTube tutorials, connecting via the WordPress REST API or other external CMS (Data Variables) is usually done in the BODY. Does it have to be this way, or can the data source be added, for example, in a section of the page? Does this affect performance?

7 comments

OOleg Isonen

its only a matter of where you want to access it, you want to define it close to where you use it or globally on body if its for the entire page

OOleg Isonen

or on the root if its for every page

BBogdan

Only global root and body variables can be accessed from page settings

rrsppl

What does this mean in practice?

rrsppl

Does it matter where I place them in terms of website performance? And does the number of them make a difference? I'm asking about WordPress and the REST API. GraphQL, based on the WebStudio video on YouTube, seems a bit more complex to me.

OOleg Isonen

If you need to bind that data in page settings, you will need to put it into body or root

SSteve Suderman

My advice would be to start with one of the pre-built integrations. So if you're using Wordpress, use that one. Open Webstudio and start a new project. Then on the side select the integration from the marketplace. And generally i would recommend creating your queries on the body so they are all in one place and easy to find. Unless you have certain calls that are going to happen on every page (like a list of featured posts, or whatever). In that case create it on the root and it will easily be available on every page. In terms of performance I don't think it matters much if you call on the body or if you call later in the DOM. Either way it's getting called.

Attachment

Add a reply

Join the Webstudio community

Connecting to External CMS