Tim I have some notes on this, hope it's ok to tack them on here.

Approach possibility-
- Essentially a single site-level "CMS record" with the exact same field types ( switch, color, text, image, richtext, number, url, select option list, CMS ref, CMS multiref, etc ), that is available site wide
- The ability to override these values at the page level, and possible folder level
- Make it fully bindable to elements ( text, color, link, etc ) and component properties, the same as a CMS or parent component context
- API access so you can get/set variable values remotely
- Per-field option to emit variable values into an object defined under window. so scripts can access it

Use cases-
- Store the phone number and main email in one place, to minimize typos
- Centralize logo SVG
- Centralize hours of operation ( 7 Mon - Sun fields or 1 richtext )
- Store key URLs like automation webhooks, which could change
- Deal of the day, with a URL field linking to an individual page or CMS item
- Shorten the path between theme-purchase and site-build by allowing users to just change a few key vars and their site is mostly functional
- Switch on-off "buy this template" badges that template builders like to add. Bind a switch to settings visibility.
- Turn on and off a site-wide modal alert, for businesses that struggle with things like capacity issues, staff issues, stock availability issues "New shipment arriving today!" etc.
- Pop-up switching. Easy ability for the front desk to change the pop-up that is displayed. A select for non, plus 2 or 3 themes, and then richtext and button URLs for content editing. Edit in one place, through build mode, with no designer complications ( modals are tricky there ).
- Change aspects of the styling according to today's weather. Automation just pushes an update to a site var, which is a class name or connected to variables, etc.

This is essential for site management. Especially for prices and phone numbers!

This is a must for things like APR's, or prices that you want to change in just one place to make it easier to manage the entire site

Please make it!

Since I can't vote again, I'm just gonna comment again. This is desperately needed and should be simple enough to implement.

This is very needed so that clients can edit these themselves in the editor.

This is so needed for things like centralized emails, phone numbers, etc.

Yes! This feature will allow clients to change their phone numbers, email addresses, etc., in one place and automatically change every element that is referencing to them.

To my last comment, adding API to the needs for get/set these vars. Which of course means, Logic as well.

The use case I'm currently facing is a requirement to generate aggregateRating JSON+LD markup. Ratings are in a collection, and all are scored, but there's no internal way to get an average and bind it into my markup.

I can have that calculated externally through Zapier/Make or hopefully via Logic someday, but where to store the resulting average value? It needs to go into a global var that I can then include in my site.

NICE. I just came here looking to add this wishlist item.

Ideally these vars will need to be strongly typed, e.g.;

• strings, e.g. for site name

• emails, e.g. for support@mycompany.com

• numbers, e.g. "X" customers served

• phone numbers

• measurements, especially to support Interactions, where several different parts of an animation need the same measurements e.g. open/close animations

• timing durations, also for animations

We'd want the ability to reference these variables from;

• Designer elements, as appropriate for content, links, emails, default input values, etc.

• Page config elements, like {{ var.sitename }} in Page titles

• Scripts, via webflow.js

Related - https://wishlist.webflow.com/ideas/WEBFLOW-I-1787

This is going to be useful for us, we have 2 sites (1 for staging, 1 for production) for each of the env i would like to add redirection link to its specific env, eg.

• Staging -> Staging

• Prod -> Prod

Tested the design in staging, export and import to Prod

With env variables set for the redirect link domain, it doesn't impact the link(reference to global variable), when I export and import my pages from Staging to Prod

Currently we have to update the link manually everytime.

Another use case: for pricing info

e.g. we often mention starting prices for products and service in our copy all across our site (where a CMS or symbol doesn't make sense). It would be great to have this updatable from one location.

I have found a way to do this realtively easily with JavScript and I SUCK at Javascript. I have a snippet of Javascript that changes the Copyright Date on everypagel. Every year it will update itsef. I tried this with just using the company name and it works. It is done on page load so I am not sure the SEO implications/impact. Also this is great for pricing if you do not have enough items to warrant a CMS site - I.E. I have a customer that has one product and is going to sell via PayPal but I want to be able to advertise the price everywhere and not have to worry about changing 50 places or missing one change down the road.

I am not sure I can paste the code in here so message me and I will send it to you.

This can be done in a very crude way, using a JSON chunk in your site header, and script to search/replace specific areas you want to apply it. But that's very ugly and prevents clients from managing those variables through the Editor interface.

I have a similar need for popup notifications, with a chunk of richtext and the ability to turn that alert on/off.

Yes please

Reallllly need this one. Any update? If not, can this be achieved by a script?

Is there any way we could do a workaround on this with the CMS?

Yes, please

More Use Cases:

• Company Name
• Company Address
• [named] Email Address

Related:

Style Variables: https://wishlist.webflow.com/ideas/WEBFLOW-I-55
Symbol Variables: https://wishlist.webflow.com/ideas/WEBFLOW-I-1558