Ease of use for Content Team, developer independenceģ. While evaluating we were looking at these key criterias:Ģ. Performance and user experience can easily go for a toss considering content team may not be diligent with everything outside the scope of the content
#Contentful json editor code
Code reusability perspective - impacts performance in a longer runģ. The content team as it requires some level of technical skillsĢ. While WordPress is a very fast, intuitive and comprehensive tool to power static pages, it's not ideal for:ġ. We were working with WordPress at that moment and for some parts - we still do. I'd like to share my experience for a similar use case.Ī couple of months back I was in a similar place while facing some similar set of challenges within our SEO and Content Team.
It is it’s greatest strength and not a weakness though See more How you present it is not handled by contentful. It’s just a cms for structuring your data. You can integrate it with any app, whether it be serverless, on a vm, or inside a docker container.ĭownside is the front end is really up to you. No being constrained to the CMS’s programming language or hosting environment like with Wordpress (to an extent, wp has an API too). No messing about compilation, Java, maven, like with AEM. It won’t stop you from using MySQL or any other technology alongside it. There is service integration with common apps, or data sources.īecause it’s just an API call, you can use literally any tech stack with it. And then the API will just return a list of content items in JSON array or object format. Content types is just a definition of how a content item is structured, you can add fields such as title, unique id, image, rich text, lists of child content items, etc. Image hosting / cdn and resizing? No problem. Entire landing pages consisting of sections that have child items in them and attributes for each child? Not an issue. Architectural portfolio with square footage attributes? Check. It makes no assumptions about how your data is presented or structured, and you can form any kind of content in the interface. It consist of an user interface with an API a front end app can retrieve data from. Of all the content management systems out there, contentful seems to be the most flexible. We're fairly confident for the SSG ( Gatsby), but we're still uncertain which CMS we should choose. Solution: We're considering an SSG + Headless CMS combination. "Advanced marketing features" like these: Non-devs should be able to handle content autonomously, Should have a non-dev friendly interface, should allow creating a library of reusable components/modules, should show the preview before publishing, should have a calendar with all publications, should show the history/tracking, should allow collaborating ( Google Docs like), should display characters limit optimized for SEO. This CMS should have fairly advanced marketing features: either natively built, and/or be open source, so we can either find third parties' plugins suiting our needs or build our own plugins homebrew. Problem: As our Marketing team gets growing needs to publish content fast and autonomously, we're trying to add a CMS to our stack. const contentful = require('contentful') Īsync function getBlogFromId(blogId: string, frontasticContext: Context) ) Ĭonst response = await contentfulClient.Hi StackSharers, your help is dearly needed as we're making a move to which we will commit for the next few years. You must use require with the contentful package. To get the blog data from Contentful Delivery API, implement a getBlogFromId function which takes the blogId and frontasticContext and returns the data fields from Contentful response data.
#Contentful json editor install
#Contentful json editor how to
0 kommentar(er)
