There are two approaches to registering JSON forms with Tina. In the example below, we will cover how to work with the useJsonForm
hook.
useJsonForm
is a React Hook for creating JSON Forms. This hook works for functional components that source data from a static query using Gatsby's useStaticQuery
hook. It also works with functional page components, using a page query.
useJsonForm
only creates a form. In order to interact with the form, you must register it with the CMS. There are two main approaches to register forms in Tina: page forms and screen plugins. Please refer to the form concepts doc to get clarity on the differences. In the examples below, we will only use theusePlugin
hook to register the form.
As it's first argument, useJsonForm
accepts the data returned from a Gatsby dataJson
query. The second argument is a formConfig
object; we will cover that in the next step.
Similar to other form helpers, this hook returns the data to be rendered in the component and the form
connected with those editable values.
In order for the JSON forms to work, you must include the following fields in your dataJson
graphql query:
rawJson
fileRelativePath
An example dataQuery
in your template might look like this:
query DataQuery($slug: String!) {
dataJson(fields: { slug: { eq: $slug } }) {
id
firstName
lastName
+ rawJson
+ fileRelativePath
}
}
Any fields that are not queried will be deleted when saving content via the CMS.
Below is an example of how to use this hook:
usePlugin
& useJsonForm
hooks.useJsonForm
with the return data from the dataJson
query.useForm
and passing the form
returned from useJsonForm
.rawJson
and fileRelativePath
to the dataJson
query.src/pages/page.js
// 1. import `usePlugin` & `useJsonForm`
import { usePlugin } from 'tinacms'
import { useJsonForm } from 'gatsby-tinacms-json'
import { graphql } from 'gatsby'
export default function Page(props) {
// 2. Create the form
const [data, form] = useJsonForm(props.data.dataJson, FormOptions)
// 3. Register the form with the CMS
usePlugin(form)
return (
<section>
<Wrapper>
<h2>{data.hero_copy}</h2>
<p>{data.supporting_copy}</p>
</Wrapper>
</section>
)
}
// 4. Add the required query parameters
export const pageQuery = graphql`
dataJson(fields: { slug: { eq: $slug } }) {
id
hero_copy
supporting_copy
rawJson
fileRelativePath
}
}
`
After creating and registering the form in your component, restart the dev server and you should see a form in the sidebar populated with default text fields in the sidebar. Try editing one of the values and watch it live update on your site.
Note: You will only see the associated form in the sidebar if the component is currently rendered on the page.
To customize the form with different fields, you can pass in a config options object as the second parameter. Let's do that next.