FAQ / Best practices

In some cases, you might need to change a field from one type to another, for example, from "short text" to "long text". As it is not directly possible to change a field type, a migration will be needed. You could conceivably do the following:

1. Create a new, temporary field with a random field ID

2. Use transformEntries to copy the field contents to the new field

3. Delete the original field

4. Create a new long text field with the same ID as the now-deleted field

5. Transform the entries again to copy the field contents over

6. Delete the temporary field

We recommend the following steps:

1. Export your data from the existing source

2. Format the data programmatically to what your content model accepts

• The files should be converted to JSON format

• It would be beneficial to create a content model and some dummy content in a test space, then use the export tool to generate a JSON dump of it. Inspecting that JSON will provide insights into the data structure, which will help develop the custom parser.

3. Import the data to Contentful using the import tool or via Content Management API SDKs by creating and publishing each entry iteratively

1. Check out the list of partners available on our website: All partners listed on this page have verified client references and in-house Contentful experts.

2. Post in Contentful Community: You can post here and some Contentful customers might make recommendations. Please note that references will not be verified from Contentful's end.

We recommend leverage on Contentful's global CDN, so you will not need to create and maintain your caching layer. Decreasing load time is also best achieved with proper content modeling, API query structure, and system architecture design.

No, currently it is not possible to reference entries/assets from other spaces/organizations.

This is not possible respecting the X-Frame-Options HTTP response header, the web app will always send this header with a value of DENY in the response. This behavior is in place to prevent clickjacking and unfortunately cannot be changed.

We recommend using an embedded entry, on that embedded entry you can have multiple strategies to have the table content: If it's static content, use markdown field with the table; If it's dynamic content, then use a multiple reference field having references to each row of the table. In your application, you could create a custom renderer for that type of embedded entry that renders the content as tables.