In 2006, developers at Globo.com wanted to break down silos between different sites by allowing developers from other sites to offer GMC registered videos in a simple and standardized way. However, the platform's rigidity made it challenging to display dynamic video content on static HTML pages. To solve this problem, they developed standardized visual widgets on the client-side that obtained information from WebmediaAPI by returning a JavaScript call to a callback function. However, they needed server-side rendering to maintain relevance in organic searches. To achieve this, they rendered JavaScript widgets on the server using Rhino. Despite facing challenges, they successfully developed a client-side widget platform that enabled all websites to offer videos consistently and created a server-side rendered video product that could be indexed by Google.
1 comment
[ 1.9 ms ] story [ 13.7 ms ] threadIn 2006, developers at Globo.com wanted to break down silos between different sites by allowing developers from other sites to offer GMC registered videos in a simple and standardized way. However, the platform's rigidity made it challenging to display dynamic video content on static HTML pages. To solve this problem, they developed standardized visual widgets on the client-side that obtained information from WebmediaAPI by returning a JavaScript call to a callback function. However, they needed server-side rendering to maintain relevance in organic searches. To achieve this, they rendered JavaScript widgets on the server using Rhino. Despite facing challenges, they successfully developed a client-side widget platform that enabled all websites to offer videos consistently and created a server-side rendered video product that could be indexed by Google.