[{"_id":"project-settings","settings":{"translateMetaTags":true,"translateAriaLabels":true,"translateTitle":true,"showWidget":true,"customWidget":{"theme":"light","font":"rgb(0, 0, 0)","header":"rgb(255, 255, 255)","background":"rgba(255, 255, 255,0.8)","position":"right","positionVertical":"center","border":"rgb(163, 163, 163)","borderRequired":true,"widgetCompact":true},"widgetLanguages":[{"code":"de","name":"Deutsch"},{"code":"fr","name":"Français"}],"activeLanguages":{"fr":"Français","de":"Deutsch","en":"English"},"enabledLanguages":["de","en","fr"],"debugInfo":false,"displayBranding":false,"displayBrandingName":false,"localizeImages":false,"localizeImagesLimit":false,"localizeAudio":false,"localizeAudioLimit":false,"localizeDates":false,"disabledPages":[],"regexPhrases":[{"phrase":"#Jump to <var time-in-video=\"\"></var> in this episode","candidate":"#Jump to ","variables":["<var time-in-video=\"\"></var>"],"regex":"^#Jump to (.+?) in this episode$"},{"phrase":"#1 of <var total-count=\"\"></var>","candidate":"#1 of ","variables":["<var total-count=\"\"></var>"],"regex":"^#1 of ([\\d ]+)$"}],"allowComplexCssSelectors":false,"blockedClasses":false,"blockedIds":false,"phraseDetection":true,"customDomainSettings":[],"seoSetting":[],"translateSource":false,"overage":false,"detectPhraseFromAllLanguage":false,"googleAnalytics":true,"mixpanel":false,"heap":false,"blockedComplexSelectors":[]},"version":64525},{"_id":"en","source":"en","pluralFn":"return n != 1 ? 1 : 0;","pluralForm":2,"dictionary":{},"version":64525},{"_id":"outdated","outdated":{"#Webinar | How Content Builds Brands: Lessons from Paula’s Choice at web summit":1,"#Welcome back, Sylvia Mulder":1,"#After using Contentstack, the director of content, said:":1,"#A community platform vendor faced issues with Contentful’s CMS and sought a headless CMS with good support. They narrowed down a few different systems and decided to go with Contentstack because of its intuitive design and easy integration. The onboarding process allowed community platform to switch to Contentstack in less than one month.":1,"#Case study: Why did Community platform prefer Contenstack over Contentful?":1,"#Webinar | How Content Builds Brands: Lessons from Paula’s Choice at Websummit":1,"#Forrester Trends Report: Understand <span ljsid-1=\"\">developer experience</span> to improve business outcomes":1,"#info-circle":1,"#close":1,"#Se connecter ici":1,"#Vous avez déjà un compte?":1,"#Inscrivez-vous maintenant pour obtenir 2000 mots":1,"#Écrire":1,"#3 - SSR with Edge Routing Technical Implementation Architecture.png":1,"#2 - SSR with Edge Routing Technical Implementation Architecture.png":1,"#1 - SSR with Edge Routing Technical Implementation Architecture.png":1,"#We have created a sample app which implements this architecture. Please check out the <a ljsid-1=\"\">repository</a> and our <a ljsid-3=\"\">sample app</a> for more information. You can also find a detailed guide that walks you through setting up the example application <a ljsid-5=\"\">here</a>.":1,"#Example Application with Code":1,"#<strong ljsid-0=\"\">Fallbacks and Error Handling</strong>: Design robust fallback mechanisms with error handling in all the appropriate places to ensure a seamless user experience. Should any part of the system not work as expected, it’s important to be able to fall back to showing the users the default content (base entries) instead of an imprecise or incomplete personalized experience.":1,"#For the longest time, CDNs have been associated with caching. Their primary responsibility has been to stand in front of your origin servers, close to your users and serve your web content directly from there to enhance user experience, and also avoid overwhelming your origin server with requests from around the world.":1,"#<strong ljsid-0=\"\">User Data Management</strong>: Ensure secure and compliant handling of user data for personalization. Avoid storing any personally identifiable information with Contentstack Personalize to facilitate personalization decisions.":1,"#methods, but this can become cumbersome over time. Alternatively, these can be managed via":1,"#triggerImpressions":1,"#This can be done by calling the Edge SDK’s":1,"#: Now that the rendering of personalized content is taken care of, you need to track how your variants are performing. This involves triggering impression and conversion events from the browser when the user views personalized content or performs a conversion action.":1,"#Tracking Analytics":1,"#Here is a list of some things to consider:":1,"#Things to Consider":1,"#<strong ljsid-0=\"\">TL;DR:</strong> it’s essentially your CDN.":1,"#The next time any user requests the same page and is resolved to the same variants by Personalize, the previously cached web page is immediately served to the user without needing to generate it anew at your origin.":1,"#Finally, a personalized page is displayed to the user.":1,"#The response is returned to the user, passing through the Edge function once again.":1,"#The CDN now caches the personalized web page against the request URL and the variants in its query parameters for future use.":1,"#Your origin reads the variants and retrieves corresponding personalized content. It then generates the personalized page and returns it.":1,"#The cache layer does not yet have the personalized web page for the variants, and thus forwards the request to your origin.":1,"#Upon receiving the variants, the Edge function adds them to the request’s URL and forwards the request to the CDN cache layer.":1,"#The user's request is first received by your Edge function, which asks the Personalize Edge API for the user’s variants.":1,"#The diagrams visually represents this flow:":1,"#When requesting the personalized variant subsequently":1,"#What is the Edge?":1,"#When requesting a personalized variant for the first time":1,"#Let’s now take a look at how the components in the architecture work—in sequence—to deliver a personalized experience to your visitors when they visit your website.":1,"#Request Flows":1,"#<strong ljsid-0=\"\">Contentstack CMS Content Delivery API (CDA)</strong>: Contentstack's CDA delivers the content (articles, products, etc.) — both <a ljsid-2=\"\">base and personalized variants</a>. Your SSR process combines this content with your page layout or components to generate the final personalized page shown to the user.":1,"#, which handles communication with the Edge API, providing it the necessary context on your behalf.":1,"#JavaScript Edge SDK":1,"#We recommend using our":1,"#Given the user UID and other context, such as the page URL, referrer, etc., it responds with the UIDs of each experience’s variant that the visitor should see. Read more about the Edge API":1,"#is the decision engine for real-time personalization. To minimize overhead on your user’s requests, it exists at the Edge, as close as possible to your users and your Edge—the two locations where you’ll interact with it.":1,"#<strong ljsid-0=\"\">Note:</strong> This document provides a high-level overview. For details on how to use Personalize and other best practices, refer to Contentstack's <a ljsid-2=\"\">official documentation</a> and consult with our support team.":1,"#Contentstack Personalize Edge API and SDK":1,"#<strong ljsid-0=\"\">Your SSR Origin</strong>: The application server dynamically generates HTML pages with personalized or non-personalized content created in the CMS. It extracts the variant information passed to it by the Edge function and retrieves appropriate entry variants from the CDA. It does not need any user-specific context, only the variants to be displayed.":1,"#One of the Edge-based architecture’s biggest advantages is its ability to leverage this cache for personalized content while maintaining real-time personalization.":1,"#It can also detect the user's variant information in the request URL’s query parameters. If it recognizes variants it has cached before, the cached personalized page is returned to the user almost immediately. If not, it forwards the request to the origin, which generates the personalized page, and the CDN stores it for future requests.":1,"#Responsible for caching rendered pages at the location closest to your user. Once your origin generates and returns a page, the CDN cache stores a copy to serve when that page is requested again.":1,"#Your CDN Cache:":1,"#<strong ljsid-0=\"\">Your Edge Middleware Function</strong>: The Edge server, distributed globally, acts as the first point of contact. The closest one to your user is called into action. Its simple task is to receive the request, communicate with Contentstack Personalize Edge to request the user’s variants, add them to the request URL’s query parameters, and forward the request per the usual flow.":1,"#<strong ljsid-0=\"\">Your User’s Browser</strong>: A user accesses your website using a browser on their device. The browser is responsible for making requests to your domain to ask for your website and then rendering the received page.":1,"#This builds on top of a traditional server-side architecture, by adding a very lean Edge function component between your user’s browser and the CDN cache. Here are the key components of this implementation architecture:":1,"#Diving Deeper into the Architecture":1,"#This is the most robust option and will also deliver the smoothest user experience for your users by eliminating loading screens or flickers, all while enabling real-time personalization.":1,"#AWS Cloudfront (<a ljsid-1=\"\">Lambda@Edge</a>)":1,"#Akamai (<a ljsid-1=\"\">EdgeWorkers</a>)":1,"#Fastly (<a ljsid-1=\"\">Compute@Edge</a>)":1,"#Cloudflare (<a ljsid-1=\"\">Cloudflare Workers</a>)":1,"#Alternatively, if you’re hosting on your own and using a CDN, here are some popular CDN providers with Edge compute offerings:":1,"#Netlify (<a ljsid-1=\"\">Edge Functions</a>)":1,"#Vercel (<a ljsid-1=\"\">Edge Middleware</a>)":1,"#Contentstack Launch (<a ljsid-1=\"\">Edge Functions</a>)":1,"#If your website is hosted with a provider, these popular hosting providers offer Edge function options:":1,"#If you already have a server-side rendered website, adopting this architecture comes down to adding a small layer of logic at the Edge, i.e. running a small function before the request arrives at the CDN cache layer. Your current hosting or CDN provider likely already offers Edge compute options, as most popular ones do today.":1,"#This approach helps you maximize your website’s performance in terms of user experience, scalability, both in terms of serving personalized content to more users, and allowing for more personalized content on the same page. It is also the most maintainable as your website or the application grows, making it the optimal architecture.":1,"#Being Edge-ready":1,"#Since entry variants are simply entries with different content, they can be rendered exactly as your base content. This means that the code that renders the content retrieved from the CMS does not need to change at all, or even know that it is rendering personalized content.":1,"#A common Edge function can be added, which requests the user’s variants from Contentstack Personalize, regardless of the page they are visiting. On the server side, it only requires a one-time setup to extract the user’s variants added to the request by the Edge function and pass them to the <a ljsid-1=\"\">Contentstack Delivery SDK</a> or <a ljsid-3=\"\">API</a>.":1,"#To get started, this implementation requires minimal code changes in your front-end. You do not need to make any changes in your browser code to render personalized content (tracking events does require changes in browser code).":1,"#Ease of Integration":1,"#As the website (with and without personalization) is server-side rendered, it generates fully rendered HTML pages, making it easier for search engines to crawl and index your website pages.":1,"#SEO Friendliness":1,"#<strong ljsid-0=\"\">Note:</strong> Triggering new impressions and conversion events may require additional code changes, but these are minimal and can also be managed through <a ljsid-2=\"\">Google Tag Manager</a> in a low-code manner.":1,"#The architecture we recommend requires only an initial setup on your backend origin code and to add a simple common Edge function to personalize your entire website. Once set up, you can create as many personalizations and experiments as you wish without needing to change existing or add code for every new element you personalize.":1,"#Over time, the number of personalizations and experiments on your website will grow. You’ll have multiple experiments on the same page, across multiple pages. A naive approach would be to inject code in all the pages and elements that have any personalization. However, this quickly becomes difficult to manage and bloats your code base.":1,"#Contentstack Personalize offers flexibility and freedom in implementation, by being API-first and agnostic of the tech stack. As long as you can make API calls to Contentstack, you can use Personalize. However, the SSR (Server-Side Rendering) + Edge Routing architecture stands out as the best approach for multiple reasons.":1,"#Maintainability":1,"#The Edge Middleware is distributed, and designed to handle heavy traffic from around the world. Additionally, it allows you to leverage the CDN caching to serve personalized content, achieving maximum scalability by serving the majority of your traffic from the CDN.":1,"#This drastically increases the traffic to your origin server, potentially causing performance and scaling issues, as well as impacting user experience due to the time taken for a round trip from a user’s browser to your origin server.":1,"#Implementing a SSR architecture without an Edge component means that the personalization decision-making logic needs to be called from your origin. As every page view needs to check for personalization, this means that every request hits your origin.":1,"#However, with the Edge-based SSR approach, this is not a problem. The page that initially loads in the user’s browser is already personalized, based on the latest available context about the user and the experiences defined by you. This provides the smoothest possible experience for users.":1,"#This means that until the script completes its process, the user is seeing either non-personalized content or a loading screen. Once the appropriate personalized content is determined, it is then suddenly injected into the page, causing flickers as non-personalized content is abruptly replaced with personalized content.":1,"#Traditional personalization implementations work entirely in the browser by injecting a JavaScript script in the front-end code. The non-personalized webpage loads along with the script, which then gathers the context about the user, makes API calls, and then replaces or injects personalized content directly into the HTML.":1,"#Flicker-free Personalization":1,"#In this way, the Edge-based architecture helps keep your website fast and Lighthouse scores high.":1,"#As this architecture also leverages CDN caching to its fullest, it ensures that any content, personalized or not, is returned to the user as quickly as possible.":1,"#Personalize supports a wide variety of different implementation architectures. As a best practice, we strongly recommend one particular architectural pattern over the others. We believe that this architecture checks all the boxes and allows for the most robust experience.":1,"#The page that loads in the browser for the user is already personalized for them, as compared to other implementations where the base page loads first, and personalizations are applied afterward.":1,"#Making personalization decisions at the Edge, in a location as close as possible to your users, helps keep the overhead introduced for personalization to a minimum. Additionally, the <a ljsid-1=\"\">Personalize Edge API</a> has been built for high performance.":1,"#Best in Class Lighthouse Scores":1,"#If there are dynamic factors, such as date and time, that affect the personalizations on the page, this architecture also ensures that those are evaluated in real-time. To your users, the content is always up-to-date based on their attributes and personalization rules that you define.":1,"#This means the variants to be shown to the user are decided in real-time, with the latest available context. If a new attribute is set for the user just before they visited the page, it will have an impact on the content shown on that page.":1,"#As every request for a web page goes through the Edge, this architecture makes sure that the <a ljsid-1=\"\">Personalize Edge API</a> (which is in charge of making personalization decisions about which variants are to be shown to a user) is called every time a user opens or refreshes a page on your website.":1,"#Real-time Personalization":1,"#This architecture offers multiple benefits, below we have listed some of the important ones.":1,"#Why do we Recommend this Architecture?":1,"#Learn to implement Personalize in a Server-Side Rendered site with Edge Routing for improved performance, scalability, and real-time personalization.":1,"#This changed recently with the advent of Edge Computing, in which CDN providers let you run a small piece of code for a request before it hits the cache layer, enabling you to customize and enhance the response in many ways. Learn more about Edge Computing in our tech talk <a ljsid-1=\"\">here</a>.":1,"#https://ai.contentstack.com/brand-kits":1,"#Die <strong ljsid-1=\"\">Starten Sie Trigger</strong> allows you to create deployment and environment-based triggers such as create/update/delete/start/fail/complete for all projects created in Contentstack Launch.":1,"#allows you to create deployment and environment-based triggers":1,"#The <strong ljsid-1=\"\">Launch Trigger</strong> allows you to create deployment and environment-based triggers":1,"#Welcome back, Svetlana Klyuchkova":1,"#No results for <span ljsid-1=\"\">Datenbank</span>":1,"#date back":1,"#Showing <b ljsid-1=\"\">246 </b> results for":1,"#Restore a Deleted Asset Folder Deleted asset folders (along with the subfolders and assets) remain in the Trash for up to 14 days from the date of deletion. You can restore the asset folders back to their original condition before they are permanently deleted. While restoring the deleted asset folders, you can also choose whether you want to restore the entries that were deleted with it. Note: You cannot edit the structure of a deleted asset folder while restoring it from the Trash. You get a read-only view of the asset folder and all the subfolders and assets that can be restored along with i":1,"#/docs/developers/manage-trash/restore-a-deleted-asset-folder":1,"#Restore a Deleted Entry Trash maintains a backup of all deleted entries for up to 14 days from the date of deletion. You can restore deleted entries before they are permanently deleted. Once restored, you will find the entries just as they were before you deleted them. The Trash feature also provides the ability to modify entries before restoring them. This means that you can edit the content of any field in the entry and then restore the updated version of the entry. Warning: You can directly recover entries of which the corresponding content types already exist in the stack. To recover entri":1,"#/docs/developers/manage-trash/restore-a-deleted-entry":1,"#<em ljsid-0=\"\">Back</em> up Existing Content":1,"##ContentCon25":1,"#<em ljsid-0=\"\">External</em> <em ljsid-2=\"\">API</em> Lookup":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\">1245</strong></span> results for <strong ljsid-3=\"\">external api request</strong>":1,"#Server Side Rendering (SSR) with Edge Routing Technical Implementation Architecture Personalize supports a wide variety of different implementation architectures. As a best practice, we strongly recommend one particular architectural pattern over the others. We believe that this architecture checks all the boxes and allows for the most robust experience. Introduction Contentstack Personalize offers flexibility and freedom in implementation, by being API-first and agnostic of the tech stack. As long as you can make API calls to Contentstack, you can use Personalize. However, the SSR (Server-Sid":1,"#/docs/personalize/ssr-edge-routing-technical-implementation-architecture":1,"#External API Lookup The External API Lookup extension allows you to fetch resources from third-party/external apps using APIs and display the resources in a field in the content type of your stack. Thus, while creating an entry, you can select one or more resources from a list of possible values as an input value for the field. This step-by-step guide explains how to create an External API Lookup extension for your content types. Steps for Execution Add the “External API Lookup” custom field to your Stack Use your custom field Add the “External API Lookup” custom field to your stack To add th":1,"#/docs/developers/create-custom-fields/external-api-lookup":1,"#/docs/developers/set-up-stack/transfer-stack-ownership":1,"#Delete a Webhook Contentstack allows you to delete a webhook if you no longer need it. To delete a webhook, log in to your Contentstack account, go to your stack, and perform the following steps: Click the “Settings” icon (press “S”) on the left navigation panel, and select Webhooks (press “alt + W” for Windows OS, and “option + W” for Mac OS). Click the vertical ellipses in the Actions column for the webhook you want to delete, then select the Delete option from the dropdown menu. Confirm the Delete action. API Reference To delete a webhook via API request, refer to the Delete webhook API req":1,"#3 of 127":1,"#How is it different from Authtoken An Authtoken is a read-write token used to make authorized CMA requests, but it is a user-specific token. This means that your personal user details are attached to every API request that you make using the authtoken. So, if a person were to obtain access to your authtoken, and knows the Stack API key, this person would be able to make API requests that appeared to be coming from you. Management Tokens, on the other hand, are stack-level tokens, with no users attached to them. They can do everything that authtokens can do with a few exceptions for Users, Work":1,"#Keep Stacks in Sync If you have some content published on an environment (for example, “testing” or “staging”), and you want to publish the same content on another environment (say “production”) without impacting any content or code, you can do this in two possible ways. Also, cross referencing between stack is not supported while using a reference field. Even in this case, you can use the following two methods to keep your stacks' data in sync. Use Multiple Environments The first recommended way is to create and use multiple environments. For example, you can create two environments in your":1,"#/docs/developers/how-to-guides/keep-stacks-in-sync":1,"#Transfer Stack Ownership Note: Only the owner of the stack can perform this step. To transfer the ownership of a stack to another Contentstack user, a stack owner needs to perform the following steps: Go to your stack and click on the “Settings” icon on the left navigation panel. By default, you will be on the Stacks page. Click on Transfer Ownership on the top right. Enter the email address of the person to whom you want to transfer the stack’s ownership. Note: Make sure the intended user is already a Contentstack user. Click on Transfer. Now, the specified user will receive an email request":1,"#Brand Kit Management <em ljsid-1=\"\">API</em> | Contentstack":1,"#2 of 127":1,"#Personalize Edge APIBETA x.x.1 Run in Swagger Choose your region Introduction Overview The Personalize Edge API enables real-time, dynamic interactions closer to the end user by utilizing edge computing infrastructure to retrieve your personalized content and display it to your visitors on your digital properties. This documentation provides information on endpoints, operations, parameters, and responses for the Contentstack Personalize Edge API. The API allows you to set and manage user attributes, get manifest, and track events for your Personalize project. Base URL For Personalize Edge API":1,"#View Stack Details To get the details of your stack, log in into your Contentstack account and perform the steps given below: Open your stack and click the “Settings” icon on the left navigation panel. Click Stack. You will see the General section, where you can see stack details such as the Name (editable), Description (editable), and Stack Owner Email (read-only). Scrolling down, under API Credentials, you will get the Api Key of your stack. If you are the owner of the stack, you will be able to see the Delete Stack and Transfer Ownership buttons that will allow you to delete the stack and T":1,"#/docs/developers/apis/personalize-edge-api":1,"#Personalize Edge <em ljsid-1=\"\">API</em> | Contentstack":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\">1265</strong></span> results for <strong ljsid-3=\"\">api request</strong>":1,"#URL The URL field enables you to define a relative path of your webpage (for example, /home or /projects/new-project) where you want to publish the content. You can edit the field properties and set a default pattern for the URLs of the entries of a specific content type. Additional Resource: You can read more about Field Visibility Rules in our documentation where we have covered it extensively Note: If you have set your content type as Single, then you cannot set properties for the URL field. Additional Resource: To know how to use Default URL Pattern, please refer to our documentation on Us":1,"#/docs/developers/create-content-types/url":1,"#REST API Usage Enabling SSO for an organization may affect your REST API integrations, particularly the ones using Content Management APIs. It is therefore recommended that you read this section carefully. Content Delivery API For an SSO-enabled organization, Content Delivery APIs work as expected. The Content Delivery API requests are GET calls and they use the stack’s delivery tokens to fetch content. No changes are required. Content Management API Any user who accesses the SSO-enabled organization through IdP login cannot make Content Management API requests since it requires a user authtok":1,"#/docs/developers/single-sign-on/rest-api-usage":1,"#REST <em ljsid-1=\"\">API</em> Usage":1,"#Create Tokens Tokens are needed to authorize API calls. There are following types of tokens in Contentstack: Access token, Delivery token, Management token, and Authtoken. About Tokens Overview of Tokens Types of Tokens Work with Management Tokens About Management Tokens Key Features of Management Tokens Why Management Tokens How is it different from Authtoken Generate a Management Token Edit a Management Token Delete a Management Token Limitations of Management Tokens Work with Delivery Tokens About Delivery Tokens Create a Delivery Token Edit a Delivery Token Delete a Delivery Token Limitati":1,"#/docs/developers/create-tokens":1,"#Create Tokens to Authorize <em ljsid-1=\"\">API</em> <em ljsid-3=\"\">Requests</em> | Contentstack":1,"#Overview of Tokens Contentstack provides the Content Delivery API and Content Management API to retrieve and manage the content of your Contentstack account. Different types of tokens are required to authorize these API calls. Additional Resource: Here's the section that discusses the different types of tokens to help you understand which token will work for you. For Content Delivery APIs, you need to authenticate your request with a Delivery Token that has been assigned to a specific publishing environment. And, to make authorized Content Management API requests, you need to use the stack API":1,"#Overview of Tokens to Authorize <em ljsid-1=\"\">API</em> <em ljsid-3=\"\">Requests</em>":1,"#Nous le soutiendrons bientôt ! Cliquez sur":1,"#Support for downloading public videos":1,"#Lorem ipsum dolor sit amet consectetur. Morbi turpis quis lectus fames. Lacus a commodo fermentum molestie. Maecenas lectus purus.":1,"#Developer features":1,"#Code with the apps & SDKs you want":1,"#Apps & sdks":1,"#video optional":1,"#Apps & SDKs":1,"#Video optional":1,"#try for free":1,"#Aviva Solutions is a Contentstack Solutions Partners | Contentstack":1,"#images.png":1,"#Aviva Solutions":1,"#Get Stack Bulk Task Queue <span ljsid-1=\"\">NOUVEAU</span>":1,"#Bulk Add to Release <span ljsid-1=\"\">NOUVEAU</span>":1,"#Entry Variants <span ljsid-1=\"\">NOUVEAU</span>":1,"#Variant Groups <span ljsid-1=\"\">NOUVEAU</span>":1,"#Champs et Propriétés du champ":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\"></strong></span> results for <strong ljsid-3=\"\">shopware</strong>":1,"#https://cdn.contentstack.io/v3/stacks/sync?init=true&content_type_uid=for_synchronization_calls&locale=en-us&start_from=2018-01-14T00:00:00.000Z&type=entry_published, entry_unpublished, asset_published":1,"#Welcome back, Marina Mofford":1,"#E book":1,"#About JavaScript Delivery <em ljsid-1=\"\">SDK</em>":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\">387</strong></span> results for <strong ljsid-3=\"\">sdk</strong>":1,"#About Ruby Utils Library Contentstack provides the Ruby Utils library that contains all the utilities for the Ruby SDK. Features included: Embedded Object: Allows you to fetch embedded entries/assets (placed inside the “Rich Text Editor” (RTE) field) and display them on your frontend application. To learn how to embed entries/assets in the RTE field, refer to the Embed Entry and Embed Asset documentation. Note: The Contentstack Ruby Utils library supports Node.js version 10 or above. To use this Utils library in your application, follow the steps specified in the Get Started with Ruby Utils li":1,"#/docs/developers/sdks/utils-sdk/ruby/about-ruby-utils-library":1,"#About Android Utils Library Contentstack provides the Android Utils library that contains all the utilities for the Android SDK. Features included: Embedded Object: Allows you to fetch embedded entries/assets (placed inside the “Rich Text Editor” (RTE) field) and display them on your frontend application. To learn how to embed entries/assets in the RTE field, refer to the Embed Entry and Embed Asset documentation. Note: The Contentstack Android Utils library supports Node.js version 10 or above. To use this Utils library in your application, follow the steps specified in the Get Started with A":1,"#/docs/developers/sdks/utils-sdk/android/about-android-utils-library":1,"#About .NET Management SDK Use Contentstack to power content for your .NET projects. Contentstack provides a .NET Management SDK (that uses Content Management APIs) that developers can use to manage the content of your Contentstack account. This includes creating, updating, deleting, and fetching the content of your account. Note: The Contentstack .NET Management SDK supports .NET version 3.1 or later. To integrate your .NET app with Contentstack .NET Management SDK, follow the steps mentioned in the Get Started with .NET Management SDK document.":1,"#/docs/developers/sdks/content-management-sdk/dot-net/about-dot-net-management-sdk":1,"#About .NET Management <em ljsid-1=\"\">SDK</em> | Contentstack":1,"#About .NET Delivery SDK Use Contentstack to power content for your .NET projects Contentstack provides .NET SDK that Developers can use to develop .NET applications and power its content from Contentstack. The Contentstack .NET SDK uses our Content Delivery APIs to fetch content from Contentstack and deliver it to your .NET-based applications. Note: The Contentstack .NET SDK supports .NET version 2.0 or later In order to integrate your .NET application with Contentstack .NET SDK, follow the steps mentioned in the Get Started section. You can check out the sample .NET apps that Contentstack hav":1,"#/docs/developers/sdks/content-delivery-sdk/dot-net/about-dot-net-delivery-sdk":1,"#About .NET Delivery <em ljsid-1=\"\">SDK</em> | Contentsack":1,"#About JavaScript Management <em ljsid-1=\"\">SDK</em>":1,"#About Java Delivery SDK Use Contentstack to power content for your Java projects Contentstack provides Java SDK that Developers can use to develop Java applications and power its content from Contentstack. The Contentstack Java SDK uses our Content Delivery APIs to fetch content from Contentstack and deliver it to your Java-based applications. Note: The Contentstack Java SDK supports Java version 1.8 or later. In order to integrate your Java app with Contentstack Java SDK, follow the steps mentioned in the Get Started section. You can check out the sample Java apps that Contentstack have devel":1,"#/docs/developers/sdks/content-delivery-sdk/java/about-java-delivery-sdk":1,"#About Java Delivery <em ljsid-1=\"\">SDK</em> | Contentstack":1,"#About Android SDK Use Contentstack to power content for your Android projects Contentstack provides Android SDK that Developers can use to develop Android applications and power its content from Contentstack. The Contentstack Android SDK uses our Content Delivery APIs to fetch content from Contentstack and deliver it to your Android-based applications. Note: The Contentstack Android SDK supports Android version 7.0 or later. In order to integrate your Android app with Contentstack Android SDK, follow the steps mentioned in the Get Started section. You can check out the sample Android apps that":1,"#/docs/developers/sdks/content-delivery-sdk/android/about-android-sdk":1,"#About Android <em ljsid-1=\"\">SDK</em>":1,"#About Objective-C SDK Use Contentstack to power content for your iOS projects Contentstack provides iOS SDK that Developers can use to develop iOS applications and power its content from Contentstack. The Contentstack iOS SDK uses our Content Delivery APIs to fetch content from Contentstack and deliver it to your iOS-based applications. Note: The Contentstack iOS SDK supports objC and Swift 4.2 and iOS 10 or later. In order to integrate your iOS app with Contentstack iOS SDK, follow the steps mentioned in the Get Started section. You can check out the sample iOS apps that Contentstack have dev":1,"#/docs/developers/sdks/content-delivery-sdk/ios/about-objective-c-sdk":1,"#About Objective-C <em ljsid-1=\"\">SDK</em>":1,"#About JavaScript Delivery SDK Note: We recommend using the TypeScript Delivery SDK as a preferred option over the JavaScript Delivery SDK for optimal performance and enhanced functionality in your project. Learn to seamlessly migrate from JavaScript to TypeScript. Contentstack provides JavaScript Delivery SDK that Developers can use to develop JavaScript applications and power its content from Contentstack. The Contentstack JavaScript Delivery SDK uses our Content Delivery APIs to fetch content from Contentstack and deliver it to your JavaScript-based applications. Note: The Contentstack JavaS":1,"#/docs/developers/sdks/content-delivery-sdk/javascript-browser/about-javascript-delivery-sdk":1,"#https://cdn.contentstack.io/v3/content_types/product/entries/blta250054cfa4f5aab?version=4&locale=en-us&include_fallback=true&include_branch=false":1,"#<span ljsid-0=\"\">GET: </span>https://cdn.contentstack.io/v3/content_types/{content_type_uid}/entries/{entry_uid}?version={version_number}&amp;locale={locale_code}&amp;include_fallback=true":1,"#Include All References<span ljsid-1=\"\">NOUVEAU</span>":1,"#Cette requête est spécifiquement destinée aux entrées et fonctionne sur les champs qui font partie du champ Groupe.":1,"#Cette requête est spécifiquement destinée aux entrées et fonctionne avec des champs qui font partie de n'importe quel bloc au sein d'un champ de bloc modulaire.":1,"#Cette requête est spécifiquement destinée aux entrées et fonctionne avec les champs qui font partie du champ Groupe.":1,"#Cette requête concerne spécifiquement les champs qui font partie de n’importe quel bloc au sein d’un champ de bloc modulaire.":1,"#seul paramètre [Reference_field_uid][]":1,"#Cette requête est spécifiquement destinée aux entrées et aux travaux sur les champs qui font partie du champ Groupe.":1,"#Cette requête fonctionnera uniquement pour les entrées.":1,"#Cette requête est spécifiquement destinée aux entrées et fonctionne sur les champs qui font partie de n'importe quel bloc au sein d'un champ de bloc modulaire.":1,"#Cette requête fonctionnera à la fois pour les entrées et les actifs.":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\">159</strong></span> results for <strong ljsid-3=\"\">automate</strong>":1,"#Automate App The Automate App provides functionalities to integrate Automate into your stack. With the Automate App, you can bring all the capabilities of Automate to your entry editor in the CMS. Let’s see how you can use and install the Automate app via the Marketplace to get started. Prerequisites Contentstack Account Access to the Contentstack Organization/Stack as the Owner/Admin Steps for Execution Install Automate App Create an Automation Execute the Automation via Automate App Install Automate App Follow the steps to install the Automate App in Contentstack. Log in to your Contentstack":1,"#/docs/developers/automation-hub-guides/automate-app":1,"#<em ljsid-0=\"\">Automate</em> App | Contentstack":1,"#Delete a Project You can delete a project, its automations, and connected apps from Automate. Organization owner, admin, and the project owner can delete a project. To delete a project, perform the steps given below: In the left-hand side primary navigation, click the Automate icon, and click the project you want to delete. You can also filter projects based on the tags. These tags can help you filter out the projects in the Search. If you use both; a tag filter and the Project Search, then it gives a consolidated list of projects based on the search and tags. Click Settings, scroll down, and":1,"#/docs/developers/automation-hub-guides/delete-a-project":1,"#Edit a Project You can edit the primary details of a Project, i.e., its Name and Description, from the automation settings page. To edit a project, perform the steps given below: In the left navigation panel, click Settings. Enter the Project Name and Description that you want to edit and then click the Save Changes button. Note: An organization's owner and admin can edit and view all projects within automate, while organization members can only view and edit their projects.":1,"#/docs/developers/automation-hub-guides/edit-a-project":1,"#Create a Project A project in Automate, helps you organize all your automations in one location in an organized manner. To create a project, perform the steps given below: Log in to your Contentstack account. In the left navigation panel, click the Automate icon. Click + New Project. In the New project model, enter the Project Name (for example, Sample-Automation), an optional Description, and click Create. After successfully creating the project, you can start building different automations. Note: The maximum number of projects allowed per organization is 50.":1,"#Automate Connectors Automate connectors are third-party applications that can be utilized with Contentstack Automate to automate specific tasks. Here are some connectors that you can swiftly configure and utilize for automation purposes. Triggers Launch Trigger Contentstack Trigger HTTP Trigger Scheduler by Automate Sub Automation Trigger BigCommerce Trigger Box Trigger Contentstack Delivery Contentstack Delivery Contentstack Management About Contentstack Management Actions Contentstack Management - Assets Actions Contentstack Management - Branches Actions Contentstack Management - Content Typ":1,"#Automate Guides Welcome to Contentstack Automate, an automation platform that helps you automate repetitive tasks between two or more apps without the need to code. Quickstart Get Started with Automate Executing an Automation Automate AppNEW Working with Automate About Automate Automation Sharing Create a Project Edit a Project Delete a Project Create an Automation Draft vs. Live Automation Mode Edit Automation Details Clone an Automation Delete Automation Rename Trigger Delete Trigger Rename Step Delete Step Mark a Project as Favorite Conditional Paths within Automate What is a Conditional Pa":1,"#https://azure-eu-personalize-edge.contentstack.com - Azure - Europe":1,"#https://eu-personalize-edge.contentstack.com - Europe":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\">420</strong></span> results for <strong ljsid-3=\"\">workflows</strong>":1,"#Set up <em ljsid-1=\"\">Workflows</em> and Publish Rules | Contentstack":1,"#<em ljsid-0=\"\">Workflows</em> Limitations":1,"#<em ljsid-0=\"\">Workflows</em> Use Cases":1,"#Use <em ljsid-1=\"\">Workflows</em>":1,"#Cs_StrategyGuide_Forrester.webp":1,"#Contentstack is excited to announce three new powerful add-ons that will revolutionize the way you work with your favorite digital experience platform. Marketplace lets you install read-to-use apps; Developer Hub enables you to build apps, and Automate lets you connect apps and automate workflows.":1,"#This announcement page covers the introduction of three new powerful add-ons in Contentstack: Marketplace, Developer Hub, and Automate.":1,"#Introduction_image.png":1,"#To access the Marketplace, Developer Hub [Beta], and Automate, log in to your Contentstack account and check out your main left navigation menu. You should see the following icons on your screen.":1,"#<strong ljsid-0=\"\">Note:</strong> Automate is a plan-based feature. By default, each organization will be enrolled in the Explorer Plan, which is included at no cost and allows up to 200 executions per month.":1,"#You can create multiple automations that cater to your specific business requirements and group them together in a specific project. Read more about <a ljsid-1=\"\">Contentstack Automate</a> and <a ljsid-3=\"\">Automation Connectors</a>.":1,"#Automate is a workflow builder that uses triggers and actions to help you automate repeatable tasks within Contentstack and third-party apps, with no need for code.":1,"#Automate – Connect Your Apps":1,"#Your eng":1,"#August 29th, 2024":1,"#iStock-1325201442_1_1_30.jpeg":1,"#iStock-1329868977_1_30.jpg":1,"#iStock-1471755407_1_30.jpg":1,"#elastic-logo.svg":1,"#Sylvie Shimizu,":1,"#PVH-Hero-440X640.png":1,"#An outdated version detected (latest is 15.0.2), upgrade is highly recommended!":1,"#node_modules/react-dom/cjs/react-dom.development.js (26596:1)":1,"#node_modules/react-dom/cjs/react-dom.development.js (27490:1)":1,"#node_modules/react-dom/cjs/react-dom.development.js (4277:1)":1,"#node_modules/react-dom/cjs/react-dom.development.js (4213:1)":1,"#node_modules/react-dom/cjs/react-dom.development.js (4164:1)":1,"#node_modules/react-dom/cjs/react-dom.development.js (21657:1)":1,"#node_modules/react-dom/cjs/react-dom.development.js (19931:1)":1},"version":64525}]