Skip to content

Commit

Permalink
fix: updated name of package in readme
Browse files Browse the repository at this point in the history
  • Loading branch information
jjburbridge committed Nov 26, 2024
1 parent c6f6934 commit 847a8a1
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# sanity-plugin-personalisation
# @sanity/personalisation-plugin

> This is a **Sanity Studio v3** plugin.
Expand All @@ -7,7 +7,7 @@ This plugin allows users to add a/b testing experiemtnts on a field level basis
## Installation

```sh
npm install sanity-plugin-personalisation
npm install @sanity/personalisation-plugin
```

## Usage
Expand All @@ -16,7 +16,7 @@ Add it as a plugin in `sanity.config.ts` (or .js):

```ts
import {defineConfig} from 'sanity'
import {fieldLevelExperiments} from 'sanity-plugin-personalisation'
import {fieldLevelExperiments} from '@sanity/personalisation-plugin'

const experiment1 = {
id: '123',
Expand Down Expand Up @@ -239,10 +239,9 @@ with default configuration for build & watch scripts.
See [Testing a plugin in Sanity Studio](https://github.com/sanity-io/plugin-kit#testing-a-plugin-in-sanity-studio)
on how to run this plugin with hotreload in the studio.


### Release new version

Run ["CI & Release" workflow](https://github.com/sanity-io/sanity-plugin-personalisation/actions/workflows/main.yml).
Make sure to select the main branch and check "Release new version".

Semantic release will only release on configured branches, so it is safe to run release on any branch.
Semantic release will only release on configured branches, so it is safe to run release on any branch.

0 comments on commit 847a8a1

Please sign in to comment.