Jump to content

User:Dsalinasgardon/sandbox

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Dsalinasgardon (talk | contribs) at 12:58, 22 June 2018. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Contentstack
Developer(s)Buil.io
Initial releaseMay 2014 (2014-05)
Written inJava, JavaScript, Node.js, Ruby, PHP
Operating systemCross-platform
TypeHeadless CMS
Websitewww.contentstack.com

Contentstack is a headless content management system created by Built.io which provides developers, web designers, and content managers with the tools to create and manage digital content.

The platform offers the content component of a CMS, focusing on the storage and publishing of content and facilitating content workflows, organization, and collaboration.[1] Contentstack enables users to manage any kind of digital content across a multitude of channels, including web sites, mobile apps, email marketing, chatbots, in-seat & in-store displays, AR/VR, and jumbotrons.

Based on the agile software development methodologies,[2] Contentstack delivers content via APIs and is supported by a microservices-based, extensible architecture that allows third-party functionality such as analytics, translation, personalization and artificial intelligence engines to integrate with the core CMS.

History

Contentstack was developed in 2014 by Built.io as the company’s API-first CMS, making it available for both the enterprise and consumer sectors and adding new features and functions.[3]

In November 2016, Contentstack announced a redesigned architecture and group of new features, including optimization of the underlying database and integration with a Content Delivery Network (CDN).[4]

In December 2017, the platform announced another revamp, redesigning its architecture and adding new SDKs, an image delivery API, and real time entry presence.[5][6]

Headless CMS

A Headless CMS is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via a RESTful API for display on any device.[7]

There is some confusion around what makes a headless CMS truly “headless”, as vendors use the term somewhat loosely to label their decoupled or hybrid CMS systems. But a true headless CMS is one that was built from the ground up to be API-first, not a full monolith CMS with APIs attached afterward.[8]

The term “headless” comes from the concept of chopping the “head” (the front end, i.e. the website) off of the “body” (the back end, i.e. the content repository).

The headless CMS concept is one born of the demands of the digital era and a business’s need to focus on engaging customers with personalized content via multiple channels at all stages of the customer journey.[9] As the content in a headless CMS is considered “pure," because it has no presentation layer attached, just one instance of it can be used for display on any device: website, mobile, tablet, Internet of Things devices, smartwatches, among others.

Features

Contentstack is an API-first tool that manages files in the cloud and is built around a multi-tenant cloud model that enables a secure information encryption and significantly less downtime than a regular CMS.[10] A headless CMS allows developers to use any front-end tool to present digital content in ways that are not possible with a conventional CMS.[11]

Contentstack is built upon a microservices architecture to improve performance and reduce the risk of feature and system bloating and provides JSON data in a cloud of RESTful APIs and SDKs for iOS, Android, Ruby, PHP, Java, React Native, and Node.js.[12]

Contentstack headless technology allows developers to create adaptive platforms that enables quick change of the content and structure of both websites and mobile apps. The platform is also capable of pulling real-time data sources and respond to their input or contextual cues, which enables follow-up offers to customers based on location and purchase data.

References

  1. ^ 1952-, Paulsen, Karl, (2011). Moving media storage technologies : applications & workflows for video and media server platforms. Burlington, MA: Focal Press. ISBN 9780240814483. OCLC 713324818. {{cite book}}: |last= has numeric name (help)CS1 maint: extra punctuation (link) CS1 maint: multiple names: authors list (link)
  2. ^ "Agile Programming: as a CMS development Methodology". Innovative Systems Design and Engineering. 4: 13–16 – via www.iieste.org.
  3. ^ Parkerson, Stuart (July 16, 2014). "raw engineering Releases the contentstack.io Mobile first Enterprise Content Management System". App Developer Magazine.
  4. ^ "Built.io wants to challenge Drupal and WordPress with its headless CMS – TechCrunch". techcrunch.com. Retrieved 2018-06-06.
  5. ^ GmbH, finanzen.net. "Built.io Reports Skyrocketing Growth With New Customers, Partnerships and Awards For Its API-First Content Management System Contentstack | Markets Insider". markets.businessinsider.com. Retrieved 2018-06-06.
  6. ^ "Built.io and Contentstack bring on the headless CMS experience". diginomica. 2018-02-06. Retrieved 2018-06-06.
  7. ^ "Cloud-First Headless CMS: What It Is and Why You Should Use It - CMS Critic". CMS Critic. 2017-02-07. Retrieved 2018-06-06.
  8. ^ Udo., Bartlang, (2010). Architecture and methods for flexible content management in peer-to-peer systems. Wiesbaden: Vieweg+Teubner Verlag. ISBN 9783834896452. OCLC 663096792.{{cite book}}: CS1 maint: extra punctuation (link) CS1 maint: multiple names: authors list (link)
  9. ^ Pallas, Petr (2017). The Ultimate Guide to Headless CMS: Everything you need to know to choose the right CMS. Amazon Digital Services. p. 3. ISBN B0785PKY1C. {{cite book}}: Check |isbn= value: invalid character (help)
  10. ^ Winter, John. "The Benefits Of A Headless CMS". Forbes. Retrieved 2018-06-06.
  11. ^ Barker, Deane. "The State of the Headless CMS Market". Gadgetopia. Retrieved 2018-06-06.
  12. ^ "CMS Review: Contentstack". CMSWire.com. Retrieved 2018-06-06.