multiple instances of components not accepting multiple child elements (cbbb03d)
react-tinacms-editor: prosemirror image plugin is only added if imageProps was was defined (c29cc4c)
react-tinacms-editor: renamed previewUrl to previewSrc to make it consistent with InlineImage component and ImageFieldPlugin (db55a85)
react-tinacms-editor: seevral UX issues addressed for tables, headings, and the link modal (#1393) (28cfaec)
react-tinacms-editor: when InlineWysiwyg is not given imageProps then images are disabled (ebefdf1)
react-tinacms-github: an authorized user trying access a deleted branch will be prompted to switch back to the base branch (137b5ee)
react-tinacms-github: improved error modals on 404s (4a998fc)

Features

@tinacms/core: events from APIs are dispatched to the entire CMS (1a47d0b)
@tinacms/fields: ImageFieldPlugin will default to useing cms.media.store for previewSrc (a4f377c)
@tinacms/media: MediaStore's can have an optional previewSrc method (e4024d2)
react-tinacms-editor: by default InlineWysiwyg will use cms.media.store for the previewUrl (d7dbda7)
react-tinacms-editor: InlineWysiwyg expects imageProps.parse to modify the filename before inserting the img tag (1738671)
react-tinacms-github: GithubMediaStore implements previewSrc (325fdb4)
react-tinacms-inline: InlineImage defaults to using cms.media.store.previewSrc (d050e63)
react-tinacms-inline: InlineImage now works with an async previewSrc (91b8995)
react-tinacms-inline: InlineText and InlineTextarea will render children instead of input.value when cms.disabled (1ee29ab)
react-tinacms-inline: InlineTextarea now accepts placeholder (1be2566)
react-tinacms-strapi: StrapiMediaStore implements previewSrc (fe5df7d)

Readme

Source

@tinacms/core

The @tinacms/core package provides the core objects for building amazing content management systems.

Installation

Install the package

npm install --save @tinacms/core

yarn add @tinacms/core

F.A.Q.

Below are the answer to a couple common questions.

If you have any other questions, go to the TinaCMS Community page to join our Slack or open an issue on Github! Every question you ask helps us make working with TinaCMS even better :)

What does the CMS do?

The responsibility of the CMS keeps track of two broad types of objects:

Plugins, which extend or change the behaviour of the CMS.
APIs, which allow the CMS to integrate with third party services.

What? That doesn't seem like a CMS

The name CMS is a bit misleading. This object knows nothing of the user interface or the data storage layer. The purpose of a CMS instance is to provide a common connection point for the various aspects of a content management system. The CMS object effectively a vehicle for dependency injection.

Examples

Creating a CMS

import { CMS } from '@tinacms/core'

let cms = new CMS()

Registering APIs

import github from 'my-github-client'

cms.registerApi('github', github)

cms.api.github

Adding Plugins

import github from 'my-github-client'

cms.plugins.add({
  __type: 'some-plugin',
  some: 'value',
})

cms.plugins.all('some-plugin') // [{ __type: 'some-plugin', some: 'value' }]

Keywords

FAQs

What is @tinacms/core?

Is @tinacms/core popular?

Is @tinacms/core well maintained?

Last updated on 17 Aug 2020

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install