Thanks for digging deeper into this. I'm not sure I understand what you mean when you say "the images and markup are rendered, but the text isn't." I am seeing everthing for some functions but not for the jumbotron slides or the function in the Neptune template that displays the profiles on the who we are page.I worked differently for me either because I used a old azure website, so most the virtual machine it was running on, did not have a proper fix for GDI. Or because of using of a newer version of PhantomJs, I'll have to take another look at it afterwards.
Notice that it seems to have something to do with routing as the visual editor was unable to resolve the location of the profile to display it.Until the "who we are" page is rendered and a function on it is executed, the console doesn't know the relation between the data items and their urls. It is by design, but the system usually shouldn't have difficulties rendering the underlying page in the background. I just checked, if one restarts the website and clicks on a data item, the first time the page isn't shown, but it will be the second time.
By the way, I am running my site on an Azure Standard Instance and have enabled the "Always On" option so I do not have an issue with CPU usage and haven't had an issue since enabling the option. One thing that is troublesome however is the 30 - 45 second delay in loading the Services page of the Neptune Starter Site; there must be something on that page that takes a long time to load ... all other pages are almost instantaneous.That one is relatively easy to check :)
http://docs.composite.net/Configuration/Optimize-for-Speed/Identifying-Slow-Functions
Does the C1 site installed from the Azure Marketplace get automatically updated when changes are pushed up to the GitHub repository or is there some manual process we must follow?We do not update existing Azure website automatically. As for the newly created websites, the template is updated some time after each release, as it take some extra time for the Microsoft to approve a new version of a Web App.