GraphCMS is a very flexible tool. From simple i18n to full-blown website organization, it's all possible. We use for two cases: first, we use GraphCMS as a localization tool for our platform. So all text that is displayed within the platform is identified by a unique key. In Graph we put a value for each language available for each key. That way, it is straightforward to change translations and text in general. The second use case is our landing page. We have several different content blocks available, e.g., news article, video+text, picture+text, etc. In Graph it is pretty simple to add, remove or edit these building blocks and also to change the content of each block, e.g., texts or pictures. The actual visual interpretation is done in the code. Review collected by and hosted on G2.com.
You need to get used to the way of building stuff with GraphCMS. As the code makes the actual decision on how content looks in a given environment, it makes it harder to imagine the final result. However, after some time, you get used to it.
Unfortunately, we have performance issues from time to time, where loading of localized content takes some time. Also, it would be great to publish entire sets of building blocks. For example we have a picture+text block which has an own component nested for uploading and configuring the picture. If you just publish the entire building block, it doesn't publish the picture automatically. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through a business email account
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.







