Menza Mathew

Menza is a Team Lead working with the Technical Writers at Contentstack, and has been a part of Contentstack for the past six years. She holds a Bachelor’s degree in Computer Engineering and has over nine years of experience in writing and editing technical documentation.

Posts by Menza Mathew

May 23, 2022

Introducing Contentstack Marketplace: Explore, Build, Integrate

There is no one-size-fits-all solution to your content and digital experience management needs. Most enterprises today know that a monolithic or suite solution is no longer the answer. A best-of-breed system allows you to choose the tools you want for a modern technology stack that fits your unique business needs. A content experience platform like Contentstack gives you a perfect platform to tailor your content for an omnichannel world. It is easy to create content, extend its user interface, and integrate third-party apps you need to deliver a complete digital experience to your customers. And now, with the all-new Marketplace, it’s easier than ever. All your favorite apps are in one place, just a click away. Enter Contentstack Marketplace The new Contentstack Marketplace is a one-stop solution for all your integration needs. It houses pre-built apps, starters, guides and everything else you need to build a fully tailored digital experience stack. With the launch of Contentstack Marketplace, you can rely on our best-of-breed philosophy to create the platform that works the best for your brand, with features, services, apps, integrations and accelerators from the industry's leading technology and service providers. Marketplace allows you to connect apps and other services and make them work for you quickly and efficiently. Here, you'll find all the tools to help you with every step of your development process. You can find and install pre-built extensions, leverage high-quality applications and build integrations that will solve specific needs for your business. Here’s a quick video to get you acquainted with the Contentstack Marketplace! You can start using the apps right away with no new accounts or requirements. Installing these applications is quick and easy. Check out our comprehensive Marketplace guides for more details. Introducing Best-in-Class Apps Our marketplace has an exclusive range of apps listed based on various categories, including A/B Testing, Analytics, Commerce, DAM, Personalization and Translation. Popular SaaS applications such as Algolia, BigCommerce, Shopify, and Cloudinary are already among the integrated apps in the Contentstack Marketplace today, and with more on the way, the number is growing even as you read this! Here’s a glimpse of the top apps that you can work with. It’s easy to find and install apps with our user-friendly interface. Browse through the categories or use filters to quickly find the apps you need. Custom fields, sidebar and dashboard extensions and other integrations will make it easier than ever for your team to collaborate and create. If you are unable to find the app you need, you can send us a request specifying what you're looking for. How Can You Start Working With Marketplace? To access the Contentstack Marketplace, log in to your Contentstack account and navigate to Marketplace using the main left navigation. Under “Explore,” you can see Apps (which are third-party applications), Starters (which are starter-level apps based on significant technologies) and Guides (which offer step-by-step tutorials to help you create specific Integrations use cases). Clicking on each section, you will find “Filters” that help you quickly locate one of the many apps you can connect with. Installing each app listed in the Marketplace leads you through a series of steps to install the app in your desired location. To get them installed for your organization, simply follow the prompts. Note: If you do not see Marketplace in your Organization, kindly contact our Support Team, Build Apps for Marketplace While Contentstack offers many pre-built apps you can start with, you are not limited to that list. You can build apps for your own needs and publish those to the Marketplace as private (visible only to your team) or public (visible to all Contentstack users) apps. Here are some marketplace apps to get you started with. Learn more about building apps for Marketplace. What’s Next? This is just the beginning. We are constantly in the process of adding new apps to the marketplace so all our users can find an app for any use case, workflow, or requirement. In the coming weeks, you’ll be able to access many more custom solutions and extensions.

May 23, 2022

Build, Integrate, and Publish Apps With the Developer Hub

Contentstack is excited to introduce Developer Hub, a powerful platform that allows you to build apps, create integrations for your specific business needs and publish them on Marketplace. The Developer Hub (in Open Beta) is an app development platform that comes with Apps APIs, SDK and other tools to help you build apps with ease. Using these tools, you can develop private apps (only for your organization) and public apps (listed in the Public Marketplace for any Contentstack customers to use) such as third-party integrations, Contentstack apps and more. Developer Hub: The Power to Build If you are a developer, Developer Hub lets you build apps to extend the core functionalities of Contentstack and use them in your organizations or stacks. These apps can be extensions or integration solutions (packaged as apps), with any UI location of your choice. You can decide where these apps are rendered — as a field, sidebar widget, dashboard widget, RTE plugin or other location. We have created a comprehensive guide to help you get started with building apps. We have also included tutorials for sample apps that can get you up to speed immediately. If the Marketplace apps sound similar to extensions, it’s because they are. Apps are the future of integrating and implementing third-party solutions within your CMS. Compared to extensions, apps offer advanced functionalities as they extend all the features of your current extensions and more to provide seamless integration with your favorite third-party platforms. You can learn more about how Marketplace apps are different from extensions, which one will suit your requirements and how to convert your existing extensions into apps. How Can You Start Creating an App With Developer Hub? Note: If you do not see Developer Hub in your organization, kindly contact our Support Team, To start creating an app with Developer Hub, you need to perform the following steps: Download and use our boilerplate that will set up your project from scratch using the App SDK. Install Node version 12 in the app drive. Next, log in to your Contentstack account and click on the “Developer Hub” icon that you see on the left navigation panel. You'll see the Developer Hub landing page where you can start setting up your app. Configure the OAuth, UI locations and Webhooks. Once set up, install the app in your organization or stack according to your setup. Now, update the boilerplate code to suit your application’s needs and test it out. For more information on how to create and manage your apps, see our extensive Developer Hub guide. Contentstack Marketplace and Developer Hub: The Dual Advantage Contentstack Marketplace is a platform that allows you to connect apps and other services and make them work for you quickly and efficiently. These applications are easy to install and have all the resources you need for every step of the development process. Currently, Algolia, BigCommerce, Shopify, and Cloudinary are among the top integration apps that you will find in Contentstack Marketplace, with more to come soon. With Contentstack Developer Hub, you get the ability to create your own apps, and with the right approvals, you can even get them listed in Contentstack Marketplace so others can install and use them. For more information about this, refer to our App Submission and Approval Guidelines. What’s next? We will continue to improve user experiences with Developer Hub in upcoming releases. Also, we will provide app hosting abilities where users can upload their app code directly into Contentstack without having to rely on external third-party apps. We also plan to add more locations where these apps can be placed. Stay tuned!

Oct 25, 2021

Introducing Contentstack’s Venus React Component Library

As a flexible SaaS application, Contentstack allows developers to extend its UI and plug-in custom functionality through Experience Extensions. That, however, shouldn’t lead to developers spending excessive amounts of time and effort in developing components while trying to maintain the brand and accessibility guidelines. To that end, we are glad to introduce our Venus component library, so developers don’t have to reinvent the wheel. They can leverage our universal components — which we used to develop our newly introduced, React-based user interface — to create extensions and experiences that are truly native to Contentstack’s look and feel. What Is a Component Library, and Why Did We Create One? A component library, in general, is a library of styles and components used while developing an app, website, or any other digital property. It includes all components available throughout the app, such as buttons, input fields, alerts, and a lot more. Such a repository serves as a single source of truth for the organization and users extending your app. At Contentstack, we started building this library when we began designing our new interface. Since Contentstack is a vast product with several modules for developers and content managers, rebuilding it from the ground up involved rethinking every single component.  We knew from the beginning that when different teams (using different tools) collaborate to create different parts of a single app, it becomes easy to get lost in the process — and lose out on crucial factors such as consistency and reusability. And that could soon spiral into a mess. How We Created the Venus React Component Library To streamline the process of creating the component library, we started with a design system based on the popular Atomic Design principle. We started defining the atoms, molecules, and organisms, which made designing templates and pages easier. (The design system will be publicly available soon.) And based on the design system, we built the components. We defined the style, specs, and details of every component before rebuilding the app. For easier usability, we chose React Storybook to build our component library with. Storybook provides an excellent playground to showcase the components and makes it easier for developers to understand, build, and visually test reusable, isolated components to develop entire UIs with minimal effort. Advantages of Using the Venus Component Library Here are some advantages to using the Venus component library: Easy accessibility Consistency Speed Compatibility Minimal third-party dependencies Where to Find Our Venus Component Library This is just the beginning of our journey in creating the perfect component library. With this release, we are making the most critical components publicly available. More components are on the way. For general information about the library and to begin using the components, please visit our Venus Component Library.

Jun 26, 2020

Introducing Postman Collections for Contentstack APIs

We’re excited to announce the release of the Postman Collections for our Content Delivery, Content Management, and GraphQL APIs. These collections let you connect to your Contentstack accounts and try out our APIs. This article introduces you to Postman and walks you through the process of testing Contentstack APIs using the newly-released Postman collections. About Postman Postman is a popular API client that lets you build and test APIs through its easy-to-use GUI. With Postman, it’s easy to write test cases, inspect responses, and do a lot more. About Contentstack Postman collections Contentstack Postman collection is a set of APIs that you can import and start using instantly. We have released collections for our Content Delivery, Content Management, and GraphQL APIs. These collections come with predefined environment variables to help you get started immediately. The process to start using Contentstack Postman collections is relatively simple: Download Latest Contentstack Postman Collections Configure Environment Variables Make an API Request in Postman Update Your Postman Collection Let’s look at them in detail. Step 1 – Download Latest Contentstack Postman Collections It is imperative to have the latest desktop version of Postman to use Contentstack Postman collections. After installing Postman, you can download the latest versions of the Postman collection. To download and import the collection into your Postman app, click on the respective Run in Postman button: Content Delivery API Content Management API GraphQL API Note: For Windows, downloading the Content Management API collection doesn't download the environment automatically due to the larger size of the environment file. Consequently, Windows users need to download the Content Management API - Environment file manually and import it in their Postman environment. These collections cover all the Content Delivery, Content Management, and GraphQL API endpoints for Contentstack. You can even download the Postman collection from our GitHub page. You can follow the instructions given in the Postman collection Readme file for more details. Step 2 – Configure Environment Variables When you download and import the Postman collection, you download and import the related environment as well. Set your Contentstack account-specific values for the required environment variable. If needed, you can add your own environment variables. As the environment variables are referenced across multiple API requests, once you set the variables, it becomes more convenient to make repeated use of the Postman collection. Adding Environment Variables To add and set up your Postman environment variables, perform the following steps: Identify the environment variable(s) that you want to define. In Postman, click on the “Manage Environments” settings cog at the top-right corner. Click on the Environment in which you want to add your variable(s). Under the VARIABLE field, enter the name of the environment variable, for example, api_key and add in the INITIAL VALUE field. Enter your Contentstack account-specific value that will replace the variable when making the request. Once you have defined all the required environment variables, click on Update. Note: We strongly advise against storing your API keys and tokens in your collection permanently. If you or someone else shares the collection by mistake, other users will be able to export it along with these keys. We recommend that you provide your Contentstack account-specific API keys and tokens in your environment or directly to the sample requests. Adding Authentication Details in Environment For users who use authtoken to authenticate their requests, when you make the Log in to your account API Request, your authtoken will be saved in cookies and automatically added to your collection variable. If you want to discontinue this behavior, you need to whitelist this domain, and then you will be able to access cookies of this domain in scripts programmatically. Note: To avoid this, we recommend using the stack’s Management Token along with the stack API key to make valid Content Management API requests. For more information, refer to Authentication. Updating Your Environment With every new API request added, you need to update your environment file. To get the latest environment variables, download the collection along with the updated environment file again, compare your existing environment with the latest environment, and add the new variables to your existing environment. Once you set up your environment, you are ready to make your API requests. Step 3 – Make an API Request in Postman With the Contentstack Postman collection and the environment loaded into Postman, you can now make API requests to the Contentstack API via Postman. To make an API request, perform the following steps: Select the environment with which you want to work. Select an API Request from the Contentstack Postman collection. Note: If you want to make changes to your variable, you can do it here. Next, click on Send at the top right to make the API request. The API request should return with a response under the Body tab in the bottom half of the screen. Need some more help getting started? Check out the documentations of CDA Postman Collection, CMA Postman Collection, and GraphQL Postman Collection for step-by-step instructions and helpful screenshots. Step 4 – Update Your Postman Collection To keep your Postman collection up-to-date, download the latest version of the Postman collection along with the updated environment again, and you are good to go. Watch the GitHub Channel for Updates You can also choose to watch for the latest Postman collection updates on our GitHub repository and get notifications of new releases or updates to the repository. To do so, click on the Watch button at the top-right corner of the page and select Watching. The GitHub Readme doc will help you with the steps that you need to follow. More Information For more information on the Postman collections, you can refer the following articles: Contentstack Documentation Content Management API Content Delivery API GraphQL Content Delivery API CMA Postman Collection CDA Postman Collection GraphQL Postman Collection GitHub Repository for Contentstack Postman Collection Update: This blog post has been updated on July 29th, 2020 to accommodate the changes related to the release of our GraphQL API Postman collection.

Sep 17, 2019

Introducing “Gatsby Preview” – Preview Content Changes in Real Time

We’re excited to announce Gatsby Preview — the newest addition to our Experience Extension family. The “Gatsby Preview” widget makes it easier for content managers to instantly preview content changes on their “Contentstack + Gatsby” websites. Gatsby, a modern framework for building blazing fast websites and web apps, offers “Preview” to let editors view content changes as soon as they’re made. This is a powerful tool for Gatsby-powered websites. Since you can build incredible websites with Gatsby and Contentstack, accessing “Gatsby Preview” from the CMS to view changes makes a lot of sense. The result: Contentstack introduces the Gatsby Preview pre-built widget extension. Use this extension (embedded within our product), to preview content changes in real-time. Here’s a walkthrough of how to set up a blazing fast website using Gatsby and Contentstack headless CMS, and how to use this extension within your stack. Step 1 – Set up your “Contentstack+Gatsby” Site Step 2 – Set Up Gatsby Preview for Your Site Step 3 – Add “Gatsby Preview” widget to your stack Step 4 – Test Your Gatsby Preview instance Step 1 – Set up Your “Contentstack+Gatsby” Site To use the “Gatsby Preview” widget extension, it is imperative to set up your site using Gatsby. The source code of the site needs to live on GitHub. To get started with creating your “Contentstack+Gatsby” site, perform the steps given below: Set up your site using Contentstack’s starter kit: The Contentstack provided gatsby-starter-contentstack starter kit that lets you build your “Contentstack+Gatsby” site with ease.Note: Skip this step if you’re using an existing “Contentstack+Gatsby” site. Establish a connection between Contentstack and Gatsby Preview: Use the gatsby-source-contentstack plugin to establish a connection between Gatsby Preview and Contentstack. This plugin pulls data from Contentstack and displays it on Gatsby Preview. For a detailed explanation, refer to the Getting started with Gatsby Preview and Contentstack documentation. Step 2 – Set Up Gatsby Preview for Your Site Next, authorize Gatsby Preview to access your Gatsby site. Click on Sign in with GitHub and sign in to Gatsby Preview with your GitHub credentials. Select Your GitHub Repository Once authenticated with Preview and GitHub, create a preview instance from the dashboard/sites/create page. This instance URL is where you will be seeing your content changes. Click on Select a repository, select your Organization, and then, select your site’s GitHub repository from the list or by using the search bar. Configure Your Gatsby Site Provide Gatsby Preview with the branch and publish directory that includes the gatsby-config.js file. Note: If you leave the repository field blank, it defaults to the root of the site. Set Up Environment Variables in Gatsby Preview and Contentstack Base URL after generating the “Preview” instance URL that will be generated. Then, click on Create Preview Site on Gatsby to create your instance of Gatsby Preview. This creates a shareable instance of Gatsby Cloud configured with environment variables. Now, update the Base URL of your Contentstack “Preview” environment with this instance URL. Configure Preview Webhooks Add preview webhooks in Contentstack that will notify Gatsby Preview whenever you make changes to your website. To do so, copy the webhook URL in the Settings page of your Gatsby Preview instance, and pass it in the URL to notify the field of your “Gatsby Preview” webhook in Contentstack. You can add multiple webhooks for different events, such as create, update, delete, publish, and unpublish, that you can perform on your content. Read more. Next, integrate the Gatsby widget within your Contentstack stack. Step 3 – Add “Gatsby Preview” Widget to Your Stack When creating a new extension in your stack, click on Pre-built, and select the “Gatsby Preview” widget. In the details page, provide the necessary details for the widget as per your requirement. When setting up the configuration details, make sure you pass the “Gatsby Preview instance URL” under the “siteUrl” parameter. You are now ready to use it in your entry. Step 4 – Test Your Gatsby Preview Instance Create an entry and select Gatsby Preview from the Widgets dropdown on the top. This opens the Widget sidebar. Click on the Open Preview button to open the Gatsby Preview instance URL. Once you open this URL, all the changes that you publish to your entry can be previewed instantly on this URL. Do not close the page until you are done working on the content. More Information For more information on this headless CMS widget, you can read the following articles: Contentstack documentation Contentstack Gatsby Preview widget documentation Gatsby documentation

Jul 30, 2019

Referencing Multiple Content Types

With our latest release, we have upgraded our existing Reference field to make it more flexible than before. The new Reference field now allows a content manager to add references to entries of more than one content type. What’s New with the Reference Field The Reference field helps you add references to the entries of another content type. For example, the “Author” Reference field in your “Blog” content type refers to the “Blog Writers” content type. So, while creating an entry, instead of adding the author details manually in the “Author” field, the content manager can add a relevant entry of the “Blog Writers” content type. This is how the Reference field worked until now. So, what’s new? While creating a content type, you can now link more than one content type to a Reference field. So, instead of just linking “Blog Writers,” you can also link “Marketing Writers,” “Technical Writers,” and “Legal Writers” to the “Author” Reference field. Subsequently, while creating an entry for the “Blog” content type, the content manager can add any entry from the above mentioned content types as a reference to the “Author” field. Note: Stacks created after this release will get the new Reference field by default. To use the feature in existing or older stacks, you need to upgrade the Reference field within the content type. How to Upgrade a Reference Field To start using the new Reference field, perform the following steps: Edit the Properties of the existing Reference field within the content type. Click on Upgrade. Save the entry. This allows your Reference field to include multiple reference content types (max 10 content types) in a single instance. Likewise, you can revert your upgrade by clicking on the Revert button provided in the properties section. This will downgrade your Reference field back to the older version. Refer to our documentation to learn more about adding multiple content types to a Reference field and adding entries of referred content types. How Multiple Content-Type Referencing Affects Functionality Upgrading your existing Reference fields results in API changes. The primary change is that the input format of your Reference field changes from an array of strings to an array of objects. The change in the Reference field format is as follows: OLDNEW{   ... "ref_field": ["entry_UID1", entry_UID2,...]   ... } {   ... "ref_field": [{   "uid": "blt1111fe11e111111f",   "_content_type_uid": "footer" },{ }, ...   ... } You can refer to the API Changelog document for more details. SDK Users If you have used an SDK for developing your digital property, you will need to update the SDK to the latest version to start using the upgraded Reference field. Refer to our SDK documentation for more details. DataSync Users We have updated DataSync and added support for the new Reference field. DataSync users can refer to the DataSync documentation to learn how they can start using the new Reference field. Helpful Resources If you haven’t tried it yet, log in to your Contentstack account and check out the new Reference field. For more details, refer to the links below: Documentation link Change in API Requests

Mar 15, 2019

New IdP Role Mapping in Contentstack Single Sign-On..

If you have a well-established way of managing users and roles within your SAML Identity Provider (IdP), there’s good news. Contentstack now supports mapping your IdP roles to Contentstack roles, enabling you to keep using your existing role management (on the IdP side) for your SSO-enabled Contentstack organizations. How IdP Role Mapping Works with Contentstack SSO By mapping your IdP roles to Contentstack roles, you define the organization-level and stack-level permissions that the users of your IdP roles would have in Contentstack. The users of your mapped IDP roles can then directly log into your SSO-enabled Contentstack organization with the assigned permissions. This role mapping eases the process of managing users and roles for your IdP as well as Contentstack admins. Here are some of the other advantages of enabling IdP Role Mapping for your SSO-enabled Contentstack organization: Direct login for IdP users If your IdP roles are mapped to Contentstack roles, all users of the mapped roles can log into your SSO-enabled Contentstack organization directly. You do not have to invite them separately. This saves a lot of time and effort for the IdP admin. User management from one central location Managing users from your SSO-enabled organization becomes easier as the user management for both IdP and Contentstack can now be done from the IdP. As an admin, it eliminates the need to maintain separate lists of users for different accounts. Enhanced security If ‘Strict Mode’ is enabled for your SSO-enabled organization, inviting, updating or removing users from Contentstack is not allowed. This ensures that admins, members or developers of your Contentstack organization or stack cannot manage users or roles unless they have such rights in your SAML IdP. How to enable IdP Role Mapping for your Organization To enable IdP Role Mapping for your SSO-enabled organization, follow these simple steps: For the initial set up, refer our general guide on Single Sign-On. Go to the User Management section of your Organization’s Single Sign-On (SSO) settings page. Click on the Advanced Settings option to expand the IdP Role Mapping section. In the Add role mapping section, click on the ADD NEW MAPPING link and add the following details: IdP Role: Enter the unique identifier (name or UID) of the IdP group/role for which you want to create the mapping. Organization Role: Assign an Organization-specific role to the IdP group/role, for example, ‘Admin’ or ‘Member.’ Stack Roles: Assign stack-specific roles to the mapped IdP group or role. Finally, enter the Role Delimiter your IdP uses to delimit the users of the role. Likewise, you can add multiple mappings to map various roles of your IdP. Switch on the Enable Role Mapping toggle button to activate the Role Mapping feature for your organization. Once you do this, and save your settings, all users of your IdP roles (that are mapped) will be able to login to your Contentstack organization via SSO Login, and access the stacks with assigned rights. Read more about SSO and IdP Role Mapping in our SSO guide.

Jun 05, 2018

Introducing Microsoft .NET SDK Support for Contentstack

We are excited to introduce the Microsoft .NET SDK! This new addition to our SDK family makes it easier for customers and partners to create compelling apps and websites powered by Contentstack with speed and agility. Before the introduction of our Microsoft .NET SDK, developers would have had to write an API wrapper around Contentstack’s extensive library of RESTful Content Delivery APIs. Using this SDK, Contentstack’s customers and partners who are performing deployments in .NET can accelerate their time to market. .NET is a framework developed by Microsoft that runs primarily on Microsoft Windows. It contains an extensive class library called Framework Class Library and it provides programming language interoperability across many languages.  Using the new .NET SDK, you will be able to create .NET apps that will fetch content from Contentstack and deliver it to your applications. The SDK uses our Content Delivery APIs and has several inbuilt methods so that you don’t have to reinvent the wheel. Getting started with .NET SDK To use the .NET SDK, you will need to install the SDK and then initialize it. You can then execute queries for your app. Step 1 - SDK Installation and Setup To use the .NET SDK, perform the steps given below: Open the terminal and install the contentstack module via ‘Package Manager’ command as follows:PM> Install-Package contentstack.csharp Or, you can do this via ‘.Net CLI’ as follows:dotnet add package contentstack.csharp Add Namespace to your classusing Contentstack.Core; // ContentstackClientusing Contentstack.Core.Models; // Stack, Query, Entry, Asset, ContentTypeusing Contentstack.Core.Configuration; // ContentstackOptions Step 2 - Initialize SDK Specify the API key, Access token, and Environment Name of your stack to initialize the SDK: // Initialize the ContentstackContentstackClient stack = new ContentstackClient("api_key", "access_token", "environment_name");OR var options = new ContentstackOptions() { ApiKey = "<api_key>", AccessToken = "<access_token>" Environment = "<environment>"}ContentstackClient stack = new ContentstackClient(options);Once you have installed and initialized the .NET SDK, you can start getting content in your app. Start working with your app Try out basic queries to deliver content to your .NET apps. We have created in-depth documentation on how to get started with this SDK. You can find more details in our .NET SDK guide. With the addition of .NET SDK, we hope to enhance your developer experience. Users can leverage the full power of the .NET platform by trying out our demo app. To see the SDK in action, check out our example app.

Oct 14, 2017

More Tools for Developers: Image Delivery APIs and New SDKs

This week, we released a set of powerful new features for Contentstack. Here's a summary of the updates. Bringing “Organization” Aboard Introducing Organization, a single dashboard to manage all your users and your sites. An organization contains all of the elements – stacks, users etc. – available in Contentstack. All stacks (and the resources within) of a group or a company now belong to an organization, giving you better control over your subscription. You can add new users to your organization, assign roles, view overall usage, and macro-manage your project with ease. Read more about its features or learn how it works. Image Delivery API - Edit Images on the Fly Using this new API, you can perform dynamic actions on saved images by passing simple parameters. Some of the actions that you can perform on images are resize and/or crop, change device pixel ratio or quality, reorient images, or place an overlay image. Read our documentation on the Image Delivery API and try out the various parameters. Introducing New SDKs With the addition of four new SDKs to its arsenal, Contentstack is now stronger, better, and more powerful than ever. We have introduced Java, Ruby, PHP and React Native SDKs, so that developers can choose from a wide range of platforms to create awesome projects powered by Contentstack. Go through our documentation to get started with your favorite language Set Limits to Multi-Valued Fields We have introduced a new field parameter, "Set Maximum Limit" for the "Multiple" field. The Set Maximum Limit property allows you to limit the maximum number of instances that can be created for the Multiple field. If a user tries to create instances that exceed the specified limit, they will be warned about it. Read more about this feature.

Oct 14, 2017

Image Delivery APIs and What You Can Do with Them

When it comes to websites or apps, images are one of the most powerful ways of representing ideas and attracting visitors. Unfortunately, images often comprise the major portion of the data downloaded when loading a webpage or app. Hence, it is critical to optimize your images and their delivery to suit the respective channel (e.g. mobile, web, IoT) and destination device (browser, smartwatch, mobile app) to offer the best performance and user experience. We’re excited to introduce you to the "Image Delivery API": your magic tool to modify images on the fly. Today we’re introducing a new set of APIs that let you manipulate and optimize images while delivering them as content to your site or app. By adding parameters to the delivered Image URL, you can enhance the quality of the image, create thumbnails, trim, resize, crop, change format, and do a lot more. When you do this, the transformations happens on the fly, and the manipulated images are cached in the CDN for future use. By using the images API, you can deliver several different versions of the same image to your website or app without replacing the original image saved in your CMS database. So what can you modify with the Image Delivery API? Quite a bit. Here’s the full list: Resize (set height and width) Crop Trim Reorient Convert format Control quality Automate optimization Overlay image Add padding and canvas Apply background color Change device pixel ratio You can also combine parameters to perform multiple actions at once. Give It a Try To best understand how to use the new image delivery API, we recommend you visit our documentation site, where you can learn about and try each parameter. Once you get the hang of it, you can use these functions in your app by adding the parameters to your image URLs. Go to Image Delivery API documentation

Sep 12, 2017

Why Every Enterprise Should Consider A Headless CMS

Not long ago, a compelling website was a company’s main – and for many, the only – concern on the path to embracing ‘digital’. Nowadays, a sleek website alone does not cut it anymore and instead, organizations are faced with engaging their audiences via a plethora of digital channels, transcending mobile and IoT, spanning a huge variety of screen types and sizes, and increasingly pushing the boundaries of end-user experiences through novel technology such as AR and VR. Because of these trends and changes, many organizations and content providers are applying new technology to deal with the age-old challenge of delivering the right information, at the right time to the right place & person. A powerful tool in this quest turns out to be a new class of content management systems, variably dubbed API-first headless/decoupled CMS, since this solution provides the flexibility to deliver content in realtime on any channel. Headless CMS Benefits Even if you don’t have a plan for the future and omnichannel production, headless CMS is still an extremely helpful choice for the web – and when the time comes to make the leap to mobile, IoT, AR, VR and beyond, you’ll be ready. A headless CMS architecture is built to be flexible since it’s API-based. Being able to point content to any screen is the single best way to prepare content providers for the future of all screens. Here are a few concrete advantages of leveraging a headless CMS when it comes to delivering content across any channel. Think Past Mobile and Web Even if your audience is primarily on the web today, eventually you’ll need to go beyond your site and foray into mobile or IoT. Smart organizations have already shifted toward a mobile-first mentality since that’s where most people search. But soon, the web, and even mobile won’t be enough. Organizations need to start thinking about creating engaging digital experiences and providing content on all sorts of screens, devices, and mediums, like marketing kiosks, in-store displays, wearable devices and so on. With a headless CMS, you can point content anywhere, since APIs are endpoint-agnostic – meaning you’ll be prepared for whatever device is the next big thing. Create Once, Publish Everywhere In a decoupled architecture, content is not tied to any frontend. Instead, it’s stored as data in the CMS’s repository. This data can then be delivered to any channel through APIs. This means the content that you write once can be reused across multiple content channels. What you’ve put together on your website can be repurposed as you expand into other channels, like a VR headset or any other frontend that can accept JSON data. Build Faster Whether you’re starting a new project, redesigning one or launching in phases, a headless CMS helps you build (i.e. develop) quickly. You can start by launching a simple static website, and then gradually make it more dynamic by adding different pages in the CMS later (for instance, after a soft launch). When you’re ready, you can deliver the same content to your mobile app, perhaps once the app designs are completed). With a traditional or legacy CMS, this process would not be possible. To achieve a similar result, you’d first need to create a static HTML prototype and then convert it into the template that the CMS understands. Ultimately, working with a headless CMS means you’ll be able to shave off a lot of time that you’d otherwise spend dealing with a system – which means you can go to market faster. The way we get information is changing dramatically and businesses have to keep up. Websites are no longer a single source of content delivery; a best practice is to adopt technologies like an API-first headless CMS that will free your content from the shackles of the traditional approach.

Aug 21, 2017

Contentstack Introduces Asset Versioning

We now offer versioning for assets. Similar to how we have been managing versioning for entries, whenever an asset is updated, a new version is created and the previous one is saved as an older version. With this new feature, you can track the history of all asset versions and can restore any previous version of an asset. Asset Versioning in Action Here's how this works. Creating a new version of an asset To create a new version of an existing asset, go to the "Asset Details" page, make the required changes by uploading a new asset, and then click the "Update" button. This will create a new version of the asset. You will need to publish the latest version to see the changes in your website or app. Restoring an older version of an asset To restore an older version of an asset, click on the "History" link in the "Version" tab located on the top-right corner of the asset page. Then, click the "View" link located beside the asset version. A preview of the previous version will appear, you can modify this version or publish it. New Fields for Assets In addition to asset versioning, we've implemented two new fields, "Title" and "Description", to asset creation to help you better organize your assets. These fields allow you to include descriptions of each asset file. Note that changing the title or description of an existing asset (and subsequently saving it) creates a new version of the asset. New "Product Updates" Page We have also introduced a new section called "Product Updates" to highlight new features and important updates to Contentstack so you’re always up-to-date and can take advantage of the latest improvements. To access this section, login to your Contentstack account and click on your profile name on the top right-hand side corner of the page. Then, select "Product Updates".

Jun 09, 2017

Introducing Folders: Manage Assets like a Pro in Contentstack

Managing assets in CMS can be tedious and time-consuming, especially if you’ve saved a lot of them. We know it’s painful, so we’ve introduced the ability to create folders in assets. This means you can group your assets based on type, project, color, size, or any other parameter of your choice. Folders in the Assets section of Contentstack work just like any other folder system: You can create new folders, rename them, save assets (files) and more folders within them, or move them easily. Below is a quick overview of how this feature works. Create a New Folder Creating new folders in "Assets" is easy. Navigate to the "Assets" section, and click the new folder icon on the top right-hand side corner of the page. Provide a name of your choice and click "Create." You will now see the new folder in the list of assets. Move an Asset to a Folder Next, you may want to move some existing assets to the newly created folder. To do this, hover over the asset that you want to move, and click the vertical ellipsis icon (the "more options" icon indicated by three vertical dots) located on the extreme right-hand side end of the asset. Pick the "Move to" option and select the folder in which you want to move this asset. Likewise, you can also move folders to another folder. Rename or Delete a Folder Renaming a folder is simple. Hover over the folder and click the more options icon. Pick the "Rename" option and provide a new title. If you want to get rid of the folder, select the "Delete." However, please keep in mind that deleting a folder will delete all the assets that are saved within it.

Jun 01, 2017

When to Choose a Headless CMS (And When Not To)

Today the market is full of a variety of CMS options, and choosing one can be a daunting task. While a headless CMS can be used to cater to any kind of content requirement (especially cross-platform publishing), there are certain cases where using an API-first solution may be overkill. We’ve compiled this guide to help you determine when to choose a headless CMS and when to stick with a traditional one. When To Consider A Traditional, Coupled CMS Headless CMS is great for almost all scenarios, save for just a handful: You have low or no changes to content: If you own a static website with very infrequent or no content changes, using a coupled CMS like Wordpress could be a better solution for your needs. Your presentation is a second thought: On a site where visual presentation is not a significant focus, you could get away with using a legacy CMS. You can’t code yourself: Since headless CMS is API-first, there aren’t many templates to leverage if you aren’t technical or are a content creator. In a case like this, using a coupled CMS is an easier way to get a head start. You don’t have developers: If you’re a marketing-focused organization and have no developers in house or the budget for an external development agency, it’s better to have a drag and drop user interface where you can build your presentation layer without knowing how to code. You’re a small business: If you’re a small operation, then a free or low-cost self-service CMS platform is best (think Wix or Squarespace) because like the above scenarios, you probably don’t have the resources to completely customize your site. But it’s important to remember that eventually, you’ll hit a plateau on these CMS platforms – especially once your business grows to the point where you need flexibility to have centralized content for more than just your web presence. Remember, headless is best for SMBs and enterprise organizations looking to empower their marketing team to generate content cross-platform in a central location. Plus, developers love the freedom and flexibility they get when they can code in their preferred language. When To Consider A Headless Or Decoupled CMS There are several cases where having a headless CMS on your side can prove to be an advantage for your business. Here are a few use cases: You need to produce dynamic content: If your digital property requires frequent content updates, going with a headless CMS is the best choice. It lets you create, update, and manage content often and easily, without affecting the presentation code. You need a centralized location for content. In a headless CMS, you can easily update just a string of text and launch the change across a jumbotron, website, smartwatch and VR headset all at once without worrying about the presentation layer. This is critical especially for things like flash sales or other content that needs to get out quickly. You’re not just focused on the web. If you need to reach your audience across multiple channels like mobile, smartwatches or a marketing kiosk, an older solution isn’t going to cut it. Unlike traditional CMS’s that come with only web page layouts by default, a headless CMS has no presentation layer attached to it. It delivers content via APIs, which means you can send your content to any medium or channel. This is highly beneficial since people consume content across different channels and especially helpful for well-established organizations that have budget for ads. You prioritize high-speed content delivery. Thanks to content delivery networks (CDNs), many headless CMS providers enable delivering content to any corner of the world in a fraction of a second. This isn’t possible with legacy content management systems that don’t expose their APIs. As a result, headless CMS is best suited for businesses that rely on high-speed content delivery. You need to scale quickly. As with any SaaS service, a headless CMS is lightweight since you don’t have to maintain a backend or bare the cost of any of the infrastructure. Instead, you can focus on publishing as much content as you need, quickly and easily. You have dedicated developers. Since headless CMS is API-first, you’ll need developers to create the presentation layer and set up the content. If your organization has a dedicated team to help develop your presentation layers, you’re ready for headless.