《Brightspot:2020无头CMS和GraphQL指南(英文版)(17页).pdf》由会员分享,可在线阅读,更多相关《Brightspot:2020无头CMS和GraphQL指南(英文版)(17页).pdf(17页珍藏版)》请在三个皮匠报告上搜索。
1、Brightspot eBook October 2020Guide to Headless CMS&GraphQLDeep Dive into Headless CMS Architecture and the GraphQL Query Language2Table of Contents5 The Origin of Headless CMS7 Considerations for Choosing Headless Architecture9BenefitsofHeadlessforTechnicalTeams10 Understanding GraphQL 16 Getting St
2、arted:The Technical Buyers Checklist3IntroductionTodays technical buyers live in an ever-changing worldone thats permanently in flux as new technologies and methodologies emerge and disrupt what was previously the new thing in place to solve the next technical challenge.Pressure to always be one ste
3、p ahead has been compounded by the need to rapidly evolve and digitally transform.How exactly do technical teams play a role in successfully creating these digital-first environments and strategies that keep their organizations ahead of the game?4Technical teams are ultimately responsible for aligni
4、ng technology to support the business mission,strategy and processes.They dictate technical standardsincluding code,tools and platformsby taking into account cross-domain considerations,long-term objectives and business process and governance.Most importantly,these teams northstar is always driving
5、transformation towards a desired future statebuilding businesses not just for today,but for tomorrow.Technical teams are,unsurprisingly,the driver of technological innovation,and tasked with enhancing their organizations resiliency.Theyre constantly thinking about how things could and should work fo
6、r an optimal experienceand optimal results.To put it lightly,this is a tall order.To meet todays demands to be digitally nimble and transformative,technical teams need a modern architecture that provides ultimate flexibility in allowing their businesses to transform for the future.This is where unde
7、rstanding headless CMS architecture and GraphQL can make an impact.This eBook explains the origin of headless CMS and why this architecture is an increasingly appealing option for technical teams.Well explain the pros and cons of the various architecture types,considerations to make before going hea
8、dless,and what role GraphQL plays in supporting headless CMS.Throughout,well detail the benefits of headless for technical teams and provide guidance for how to select the best CMS for an organizations unique needs.72%of strategists say their companys digital efforts are missing revenue expectations
9、.*Gartner5The Origin of Headless CMSHeadless CMS applications are on the risebut what is headless,and where did it come from?To help answer these questions,lets briefly walk through the different content management systems that are available to businesses today.Hybrid:Decoupled and headless architec
10、tures have paved the way for the hybrid model.With a hybrid CMS architecture,organizations and publishers have the ability to mix presentation or front-end choices.The hybrid approach offers an environment that allows users to deliver different experiences to a browser window or a device,where both
11、decoupled and headless CMS architectures can be combined.Traditional:A traditionalor coupledCMS tightly links the back end to the front end.Content is created,managed and stored,along with all associated digital assets,on the sites back end.The back end is also where website design and customization
12、 applications are stored.This content management back-end and database is bound within the same system that delivers and presents content to the end users respective devices.Headless:Headless solutions are a subset of decoupled architecture.With a headless CMS platform,there is no fixed front endins
13、tead,the solution acts as a content-only data source.This allows developers to use a combination of their favorite tools and frameworks to determine where and how content appears.Decoupled:In a decoupled environment,the back end and front end of a website are splithence“decoupled”into two unique sys
14、tems that are managed separately.One system handles content creation and storage,while the other is responsible for taking that input and presenting it to the user through a chosen interface.6The upward incline of headless CMS adoption started in 2015:the year that the public GraphQL CMS specificati
15、on was developed,opening up headless architecture to a wider audience.GraphQL has since become an open standard and is an important part of what makes headless such an attractive option for CMS applications todaymore on GraphQL later!From a broader industry standpoint,headless CMSs started to gain t
16、raction as businesses needed a better solution to engage people in personalized ways.Not only that,organizations and publishers sought to be able to reach these existing and prospective custom-ers on multiple channels across the entire buyer journeyand they needed the flexibility to do it in the way
17、s they wanted.From tra-ditional web-based applications to emerging technologies like VR or smart-home devices,headless offers an adaptable solution for future-proofing a business ability to deliver the best possible expe-rience regardless of deviceToday,across all of these channels,71%of customers c
18、rave a consistent experience,yet only 29%say they actually get it*.These insights support the idea that organizations and publishers are increasingly in need of a modern CMS solution that allows them to reach people where they are engaging in the ways they expectnot just today,but into the future as
19、 new channels and technologies emerge.*Source7Considerations for Choosing Headless CMS Architecture Despite the popularity and front-end freedom of a headless CMS,it is not for everyone.Let us explain.The best way to think about a headless approach is as a management system that solely looks after y
20、our data,and allows you to access that data.Other architecture types that are not headless involve a system that will also render a webpageor front end.This is explained well by looking at the four main components that make up headless CMS:A database where content and digital assets are stored(back
21、end);A content management back end where content is created(back end);An API that connects the content management back end to any device or channel;The ability to connect to any publishing front end,allowing organizations to have the front-end technology of their choosing.How technical teams approac
22、h headless architecture and which hurdles theyll run into depend on various factors.What type of web application is being built?What are the dynamics and skill sets on the team?What use cases and requirements need to be implemented?These are all important questions and considerations each team needs
23、 to assess and address before taking the leap in choosing which architecture best suits their business needs.If headless architecture is a fit,it needs to be implemented correctly(of course)to bring to life its intended benefits.This requires an experienced team to ensure the back end and front end
24、are well planned from the beginning,so they can sync up seamlessly later.Keep in mind,the freedom that teams enjoy when using these systems means that they are responsible for writing,debugging and maintaining everything that their rendering systems require.Traditional:Simple;ideal for text-based co
25、ntent Built-in themes and templates Customize your front endDecoupled:Fast and flexible content delivery with a specified delivery environment Rapid design iterations and simpler deployments Fewer dependencies on IT The best of both worlds in a CMS(structured back end&flexible front end)Future-proof
26、(integrates easily with new technology and innovations)Headless:Fast content delivery Provides complete control over how and where your content appears Allows developers to use their favorite tools and frameworks Future-proof(integrates easily with new technology and innovations)Hybrid:Combines the
27、benefits of decoupled and headless with ability to mix presentation or front-end choices,allowing for the most flexibility Flexible“content-first”approach encourages content reuse across different experiences and channelsComparingModern Content Management System Architectures Traditional:Content typ
28、es and delivery channels are limited Limited programming framework More time and money required for customization,maintenance and enhancementsDecoupled:More complex than traditional to configure and deploy Front end development work required for designHeadless:No presentation functionality Live prev
29、iew functionality requires both technical input and front-end coordination Reliant on additional technologies for its“head”Hybrid:Success depends on vendor implementation and execution of feature set,capital,customer base,etc.PROSCONS9A headless-only approach tends to be the best option for organiza
30、tions with robust development teams that know their way around additional technologies required to establish the front end.With the right team in placeand with the architecture implemented correctlyorganizations will quickly start to reap the benefits of a headless CMS.What kind of benefits?With the
31、 decoupling of back-end and front-end needs,implementations can be quicker and development teams can accommodate changing business requirements more easily.The front end can change completely without impacting whats happening in the back end,making it simpler and faster to integrate new designs.Busi
32、nesses with multi-national sites or a network of multisites,for example,can benefit from the ability to centralize content management within a headless CMS,which is then published via APIs to back-end-agnostic sites,applications or distribution channels.Developers can also tap into their favorite to
33、ols and frameworks to determine where and how content appears,providing freedom and flexibility to pave their own way forward.Agility:Separation of the presentation layer from the platform lets teams move faster,while separation of content and presentation helps authors and developers work independe
34、ntly,accelerating time to market.3BenefitsofHeadlessCMS for Technical Teams Flexibility:Ability to mix and match front-end content offerings,meaning the best user experience can be delivered across every device,channel and touchpoint.Resiliency:Supports organizations in future-proofing their busines
35、ses by making it easy to continually evolve alongside technology,no matter what new device or platform emerges.“Headless CMSs are ready to support technologies that will become popular in the future.Some companies are already pushing the limits of content delivery by incorporating more IoT devices,a
36、ugmented reality,virtual reality and more.A headless CMS built upon powerful APIs will be more easily integrated with the newest technologies that come out,and companies will be poised for quickly taking advantage of new audience segments.-Kaya Ismail,CMSWire10Understanding GraphQLAn important part
37、of understanding how headless CMS integrations work to provide ultimate flexibility for businesses is GraphQL.Known as the querying language that enables flexible connection with APIs to support headless CMS integrations,GraphQL enables content management and delivery to external systems,including t
38、hird-party syndication.11GraphQL is a query language for APIs andaruntimeforfulfillingthosequerieswith existing data,providing an alternative to the traditional RESTful style of web services.Whereas RESTful style tends to have looser guidelines for how an API should be structured,GraphQL strictly st
39、ructures the communication between the client and the server,irrespective of the specific data models used.GraphQLs self-describing type system enables automation in the case of changes to the content data model.What is GraphQL and why it matters for headless CMSWhat is GraphQL?12As mentioned,taking
40、 a fully headless approach comes with its own set of potential drawbacks.For each,GraphQL through Brightspots Content Business Platform offers a solution,but ultimately it will be up to developers to determine if those solutions will make headless CMS the best option to solve their unique business c
41、hallenges.Lets look at how the Brightspot Content Business Platform is configured to address specific considerations with respect to GraphQL.GraphQL ConsiderationsConsiderationResolutionGraphQL queries arent small,requiring POST requests to fetch the data.“Automatic Persisted Queries”replace large q
42、uery text with a generated ID,to which an app can then map and query each time its requested.Since rendering of the application occurs outside the CMS,live preview is difficult to implement;this makes it challenging,especially for editors,to see how their publishing changes in one system affect the
43、presentation of the site theyre working on.Brightspots preview system is extensible,supporting custom preview implementations for print templates from InDesign as well as native apps.Similarly,you can specify the URL to your app,and Brightspot will iframe it into the preview pane and pass along a sp
44、ecial preview ID.If the client uses that same preview ID when making its call to the GraphQL CMS API,then Brightspot will return data specific to the content the editor is modifying.The front-end application that uses specific image sizes is separate from the CMS,meaning its unable to access the dat
45、a it needs to run rich image editing and cropping capabilities.Users can register a configuration file of their standard image sizes,which will display their defined crops in the image editor and return image URLs from the GraphQL API.Code running in the clients browser is completely open and visibl
46、e to the public,and anyone can view the data transferred from APIs.GraphQL developers must be explicit about which fields they are fetching in order to mitigate risk,but a malicious user could still inspect the schema and make their own queries to fetch additional data not used by the app.To prevent
47、 data,potentially sensitive,from being inspected,your app needs to run server side instead of client side.Or,you can leverage Brightspots View System(which sits in between the raw Database Model and the ViewModel thats returned by the GraphQL API)to sanitize the data on the back end,thus allowing yo
48、u to continue running your app client side if you desire.13GraphQL AdvantagesThe benefits of a GraphQL CMS come down to three things:simplicity,automation and flexibility.At the same time,GraphQL CMS APIs simplify data gathering by enabling users to collect all data an app requires in a single reque
49、st;REST APIs,on the other hand,require loading from multiple URLs.In terms of automation,GraphQL has a self-describing type system that automatically reflects new fields added to a content type.This enables clients to more easily discover which data types and fields are accessible from the API,and w
50、hich are being utilized.The self-describing type system also supports features like auto-complete.Finally,GraphQL APIs operate as one continuous evolving system,meaning adding new fields and types doesnt affect existing queries,and older field versions can be hidden.Through one single version,apps D
51、eveloper-friendly for use with any front-end framework,including Brightspots proprietary front endExtensible architecture that offers ultimate flexibility to choose decoupled,headless or hybrid-headless CMS as your approach.Integration-ready and migration-friendly architecture.Custom workflows that
52、act as an extension of an existing business logic.Future-proofing for your content business platform.Weve outlined the key benefits of headless and GraphQLbut what sets Brightspot apart?get continuous access to new features which makes for a cleaner and better-maintained server code.At the same time
53、,GraphQL is flexible in that it is not limited by a specific storage engine,meaning users can create a uniform API across their entire application.Because theyre available in many languages,GraphQL engines can also be used to write GraphQL APIs that leverage existing data and code.12345Televisa Cust
54、omerSuccess SpotlightChallenge:After leveraging several CMS platforms to manage all of its digital properties,Televisa decided to replatform its sites onto one multisite,headless CMS.The ideal solution would streamline all back-end functions,give the developers full front-end control,and make it eas
55、y to create and launch future sites independently.Solution:Over the course of five months,Televisas front-end developers and editorial teams worked side by side with the Brightspot team to learn Brightspot.After migrating all of its content and creating a model with the first headless site launch,La
56、s Estrellas,Televisa replatformed a total of nine sites in just five months.Results:50%reduction in launch times,with nine sites launched in five months Nine CMS platforms consolidated to one 35 front-end styles powered by four simple fields15Getting Started:The Technical Buyers ChecklistEvery busin
57、ess is differentand there is no one-size-fits-all solution to choosing the CMS thats right for yours.To assess which CMS solution is best for your organization,technical buyers should consider the following factors.Review your optionsMake sure youve done your research and understand the differences
58、between traditional,decoupled,headless and hybrid CMS architectures.ConsideryourteamUnderstanding a headless approach requires deeper technical know-how,so determine if your team has the skill sets to successfully fulfill front-end requirements and maintain this approach.Identify your content busine
59、ss goalsWhere does your organization hope to be in five or ten years?Will you be looking to scale to different regions and touchpoints?If so,having the front-end flexibility to easily deploy experiences on new channels is a plus.WeighbusinessoutcomesSelect the architecture that ensures teams(technic
60、al,publishing,marketing,etc.)and the organization at large will experience the intended benefits of the chosen CMS.16At Brightspot,we believe in front-end freedomofchoiceto be able to choose the architecture that best suits each individual organizations unique needs.Thats why weve designed our Brigh
61、tspot Content Business Platform to operate as a traditional,decoupled,headless or hybrid CMS solution.Were here to answer your questions and guide you on your journey,whichever direction you may take.17 How Brightspot is designed to grow with your business and extend with your business logic Deployi
62、ngaheadless,decoupledorhybridheadlessCMSallfromthesameenvironment Ourworld-classDeliveryTeamandhowyoucanstartyourPOCNext StepsDid you find our Guide to Understanding Headless CMS&GraphQL helpful?You are now familiar with the technical considerations to help you select the best CMS for your organizat
63、ions unique needs.Move your business forward with a content business platform built with an extensible architecture thats built to solve your unique business challenges without having to compromise.Is the Brightspot Content Business Platform the right solution for your business?Requestademo with a p
64、roduct manager to learn more about:At Brightspot we believe technology should enable content-focused teams to work smarter,faster and more seamlessly to move businesses forward.With decades of experience in publishing and media,we help companies transform their business content and digital experiences by creating enterprise applications at scale with astonishing speed.BrightspotTeamwww.BDemoBRequest a Demo