From 1ff0c238b5bb1b5e52be19a938e74b2fd60e07c0 Mon Sep 17 00:00:00 2001 From: Jake Lumetta Date: Wed, 7 Nov 2018 10:44:22 -0600 Subject: [PATCH] Adding link for better accessibility --- docs/blog/2018-2-3-sites-with-headless-cms/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blog/2018-2-3-sites-with-headless-cms/index.md b/docs/blog/2018-2-3-sites-with-headless-cms/index.md index bc326ac980ec2..9b1c3991d0f77 100644 --- a/docs/blog/2018-2-3-sites-with-headless-cms/index.md +++ b/docs/blog/2018-2-3-sites-with-headless-cms/index.md @@ -73,7 +73,7 @@ Their sleek design impressed me: the left hand side bar and onboarding process w ### ButterCMS -I've read that ButterCMS is particularly good for blogs, and after seeing how easy it is to add metadata and SEO title / metadescription to blog posts, it makes sense why this might be the case. Sometimes there were more clicks than necessary when saving things. And sometimes the jargon in this environment threw me off. Like “object”? What is that? It’s basically a category of content. So, if I’m going to create a lot of event descriptions, the event titles will be one object, the event description, another object, etc. It's an unfamiliar and abstract word for someone new to headless CMSs. +I've read that [ButterCMS](https://buttercms.com) is particularly good for blogs, and after seeing how easy it is to add metadata and SEO title / metadescription to blog posts, it makes sense why this might be the case. Sometimes there were more clicks than necessary when saving things. And sometimes the jargon in this environment threw me off. Like “object”? What is that? It’s basically a category of content. So, if I’m going to create a lot of event descriptions, the event titles will be one object, the event description, another object, etc. It's an unfamiliar and abstract word for someone new to headless CMSs. ### Built.io (Contentstack)