gathercontent.js

A Javascript library for getting content out of GatherContent.

Install

npm install gathercontent.js

Usage

Content is written on items in GatherContent. Items are stored in projects, so the main function in this library is called getProjectData.

import { getProjectData } from "gathercontent.js"

const projectId = "project_id" // you can find the id in your project settings.
const credentials = {
  email: "your@email.com", // the one you signed up with. 😊
  apiKey: "api_key", // https://docs.gathercontent.com/reference#authentication 🔑
}

const project = getProjectData(projectId, credentials)

getProjectData returns key pieces of project data from the GatherContent API.

{
  project: {},
  folders: [],
  templates: [],
  items: [],
}

Data structure

You can understand the structure of the data by reading the API docs;

• project
• templates
• folders

Items are a little more complex;

• listing items
• getting item content

Content is retrieved and sorted into an itemContent property;

const item = {
  ...itemProperties,
  itemContent: {
    slugOfFieldGroup: {
      slugOfField: "This is content",
    },
  },
}

Slugs

This library appends slugs where helpful by converting the name. Items, templates, folders and workflow statuses all have slugs added. For content, we use the slug to help key the fields.

const item = {
  name: "Hello [world]",
  slug: "hello-world", // item name is converted
  itemContent: {
    metaData: {
      // field group name is converted
      pageHeading: "Page heading", // field name is converted
    },
  },
}

Using the name for slugs is logical but comes with a downside, duplicate names.

Duplicate names are automatically handled. For example if you have a group of fields with duplicate names the conversion will append a position to the end of the key. E.g. fieldName2.

Casing

The GatherContent api uses snake case but this library converts the data to camelcase.

const itemBefore = {
  id: 0,
  project_id: 0,
  folder_uuid: "uuid",
}

const itemAfter = {
  id: 0,
  projectId: 0,
  folderUuid: "uuid",
}

Testing

To run the tests you can run;

npm run test

When you are testing the use of gathercontent.js there are a number of helpers that can aid the mocking of http requests.

You can find these in __tests__/mocks/nocks. We utilise the nock package to do this.

Or if you wish you can also mock the implementation of functions like getProjectData so it can return a specific response for your testing needs.

Rate Limiting

GatherContent implements rate limiting (as many APIs do). This library implements a repeat and proactive rate limiting strategy, which should handle all your needs.

Feedback

If you have feedback or experience any issues, create a Github issue.

You're more than welcome to contribute to the repo. To do so fork the repo, create a PR and be sure to test your work before submitting it 🙌