![]() Just head to "Settings > API keys" and choose "Add API key" in the top right. We'll be pulling these down with GraphQL later, so I recommend making more than 1 entry to demo sorting and filtering! You can filter by your content type for a sanity check:īefore moving on, let's get some API keys for our website to use. Once you've saved this model, go and make some content entries in the "Content" panel. We'll use our "Executive Board Member" model as an example here. When you're feeling comfortable, whip up a new workspace and create a new content model of your choosing. If you're 100% new to the platform, Contentful documents a lot of core concepts over here to get up to speed on "entries" and "content models." So don't take these reasons as prescriptive for all teams! Setting up our Contentful environment Note: There's roughly 10 billion ways to build a static site these days (citation needed), with another 10 billion blog posts on how to tackle the problem. We'll dive into some code samples soon, but it's much simpler than a traditional REST endpoint. ![]() You simply define the "shape" of the content you want (with necessary filtering and sorting), and the CMS responds with the associated values. GraphQL is the perfect pairing for a CMS in our opinion.It thrives with "structured content" in particular which is great for static sites like ours! Still, if you're looking for a simplified, key-value store for your copy, there are some shiny alternatives to consider. Content types are more than flexible enough for our use cases, and the UI is friendly enough for designers and product managers to navigate confidently. Contentful is one of the more popular "headless CMSs" right now, and it's easy to see why.This is pretty promising as our landing site expands, where we might add experiences that vary by user going forward (admin portals, nonprofit dashboards, etc). What's more, NextJS is flexible enough to build some parts of your website statically, and other parts dynamically (i.e. NextJS was a great match for our frontend stack, since we were already comfortable with a React-based workflow and wanted to play to our strengths.Some readers might be scoping whether to adopt these tools at all. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |