At Jaunt, I helped build Jaunt's official website in China, localized and with VR player support.
It's written in Python Django, which is highly coupled. In the content management system, we stored all the data of each titles, playlists, layouts, etc.
For example, if you add a view in the python solution, say titles, then in the CMS (c0ntent management system) above, titles section would be correspondently added. What's more. the data of the website are not only used in official website (which is just a facade), but also used for all kinds of clients. Whenever a player in PSVR, or iOS, for instance, clicked the video. It'll keep getting URLs from this website, and keep downloading and pushing datas to client via the URL with in this website's logic.
And the database for CMS itself (Django) uses MySql, while the actual data (For example, in the column "Title", there are lots of input fields in "Resources", each one is a url for the actual location. these data uses Amazon Aws s3 to save, with Microsoft Azure cdn to boost.)
Title:
Title is hard to describe, but easy to understand. For example, Some episode S02E03 is a title. In this title page, it has all different kinds of layouts, every piece of video content is the same, but with different version of videos, top-down, left-right, 4K, 2K, for web, for PSVR, etc.
In titles data, it usually also contains how many playlist it is in, and the priority in each platform.
Playlist:
Ususally a playlist is a section in specific platform. Such as "Trending", "Music", "Horror", etc.
Some titles are in multiple playlists.
Layouts:
A layout usually is also a json file, but tells similar to css. Telling the specific platform specific layout.
Others are the fundamentals, such as Administration, filter, etc.