The Headless Revolution - where is it going?
However, Barker did emphasize the benefits of the headless model, with presentation separated from content in order to more easily utilize different media channels. He also explained that headless was easier on developers, who only need to deal with the data served up by an API (and not with a particular CMS’s rendering pipeline).
Sitecore Layout Service
However, apps created in disconnected mode can then be imported into Sitecore. Data schemas defined in disconnected mode will then be used to create the correct Sitecore template/item relationships. After importing, the developer will work in “connected mode”, wherein all data comes from a licensed Sitecore instance.
GraphQL were the low-key winners of this year’s Sitecore Symposium, being lauded in every presentation about headless and JSS that I attended. Put simply, GraphQL is a service that allows developers to refine the data returned from API calls. Sitecore describes it as “the ultimate SELECT statement.” In multiple demos I got to see how developers can use GraphQL queries to refine the format of the JSON data being sent to the front end. The GraphQL IDE, called “GraphiQL”, is also available and supported inside Sitecore, for real-time query testing.
Where does this leave us?
Although Symposium covered a lot of topics, JSS was arguably the star of the show. Sitecore knows Headless isn’t going anywhere, and with JSS they incorporate all the advantages that approach has, in addition to extending already-useful Sitecore functionality.