What is Sanity?
Sanity is the CMS (Content Management System) used to host data for RBI’s digital platforms. Sanity will host your menu, restaurant data, marketing images, navigation, footer, etc.
In a nutshell, you can customize your entire Website or App in this platform.
Look and Feel
The Content Management System is a website that can be accessed via your browser to edit your Website and App data.
We will cover the specific organization of Sanity on the next chapters, specifically on Get Started with Sanity.
Environments and Front End
Your website will always be hosted in 4 development environments:
Development
Staging
QA
Production
These are used according to the best practices of Software development, and will minimize the chances of wrong developments or wrong content configurations from being seen by your guests.
All 4 environments can be accessed via your browser and will be password protected, meaning you should request access to your RBI tech manager to gain access.
The pictures below show what you should expect to find - password protected websites, and similar content displays among the different environments.
However, development teams rely heavily on using the lower environments (Dev, Staging, and QA) to develop new features. You will find discrepancies among environments, and some features might even malfunction for short periods of time.
This should not keep you from testing all your content changes prior to moving them to Production
Please request access to your RBI tech contact for the respective links for your market
Each of the Environments also has a respective Sanity link, meaning for each Environment you will have:
One Front End Link
Which will work like your website URL where you can actually see the website.
One Sanity Link
Which will access your CMS for that environment. Making changes to Staging will affect Staging environment only.
Best Practices
Do not edit any data directly on any environment other than Staging
Whatever happens, you should never ever edit data in Production, and strongly avoid editing in QA. Staging should be your go-to environment to make any changes. Wrongly editing data in other environments will increase the chances of mistakes arriving to Production, which can cause platform breaks. Mistakes handling with the platform’s content might break online ordering, causing big financial losses. Do not forget that Menu and Restaurant data are edited in Sanity, and that brings a lot of responsibility to its users.
Edit content in Staging, test it. If everything works correctly, move to QA, and test again. Only then migrate to Production.
Do not mimic your content changes through environments. We have a tool to automate your migrations and make your job easier: Sanity Migrations Tool