0.2.1

Easily learn about available updates 🆙

We have improved the version upgrade feature.

• The update modal that was popping up too often was removed.
• We now have a new section in the navigation to let you know when an update is available. Each time a new update is available, you’ll see a red dot in this section. 🔴
• Our changelog page has been updated and dynamically displays the list of available updates, so you’ll never miss an update 😉

Bug Fixes 🚧

• Uploading screenshots to Prismic is now working again 👍
• Integration Fields in Slices and Custom Types models will not be rejected anymore.
• Fixed an issue with Slice statuses where the wrong status was displayed.

0.2.0

Moving away from Storybook 🚅

As you know, Storybook has been causing a lot of installation issues for users that weren't familiar with it. Maintaining such a dependency has been hard, both for the Prismic team creating the integration and Slice Machine users.

This is why we decided to move away from Storybook and create the Slice Simulator.

• It's an in-house solution with very minimal scope (whole solution weights less than 5kb gzipped).
• Unlike Storybook it relies on your framework's bundler. So there are no issues with your CSS solution, tools you use, etc.
• To make installing Slice Simulator as easy as possible we have created in-app installation steps to help you configure your project.

NOTE: Slice Machine will still continue to create Stories automatically for your components if you wish to continue using Storybook.

Full link field functionality

Now when adding a link field the content creators will have a choice of internal/external/media links.

We improved the way you install Slice Machine dependencies

Depending on your framework, when you use the @slicemachine/init script it now installs all the necessary dependencies to get a Prismic project up and running.

Feedback loop

We design Slice Machine features based on your experience. That's why we have decided to implement a feedback loop within the Slice Machine to learn more about your experience at the source.
This is only a small amount of information about whether you are using the onboarding and Slice Simulator.

Bug fixes

• Custom types must now be created with an id

0.1.2

Learn Slice Machine in a few slides 🚀

We created a page at /onboarding that explains the core concepts of Slice Machine. This will show up once and remain accessible anytime via the URL.

It will explain the following concepts:

• How to create a Slice
• How to use your Slices to build a page
• How to push your Slices to use them in the content editor

A new modal to rate your experience with Slice Machine 🔢

You can rate your experience using Slice Machine and give us feedback to help us improve the product.

You won't have to log in as much 🤘

To avoid having to log in every day to play with Slice Machine we implemented two things :

• Your authentication tokens will now last 48 hours.
• Your token will refresh automatically

Bug fixes

• When creating a new variation based on an existing one, the scroll in the variation list has been fixed.

0.1.1

We simplified the way you install Slice Machine

You can now easily set up a Slice Machine project using a single command : npx @slicemachine/init

This command does the following :

• Create or connect to a Prismic repo.
• Detects the project framework.
• Installs Slice Machine UI as a dev dependency.
• Creates a sm.json file that includes the Prismic API endpoint and the Slices path.
• Adds a slicemachine script in the package.json that's used to run the plugin.

You can now log in to your repository from the UI 🍾

To avoid going back and forth between your terminal and the UI. Now when you try to push your data model to Prismic and you are not connected or your connection expired, you will be asked to login with a direct link.

The prismic login command is not longer needed to connect to Prismic 🎉

The prismic sm develop is now deprecated, instead use npm run slicemachine in your project

Bug fixes

• You now have proper error messaging if you don't have correct Prismic repository access.
• The slice machine can be launched with node 12.
• Minor improvements on the start script.

0.1.0

We now support Slice variations ✌️

Variations allow you to create another version of your Slice in the Slice Machine and allow your content creators to choose from these different versions when using the Slice in the document editor.

Each variation comes with its own preview thumbnail that views will see in the Prismic writing room.
They also come with their own mock data that can also be configured separately and viewed in Storybook.

To customise the thumbnails, create a folder named after the variation ID and put your
preview.png file. Something like: slices/MySlice/default-variation/preview.png

The local builder now supports Custom Types 🎉

Yes! You can now create and update Custom Types from the local builder.

This should remove some back-and-forth between the local builder and the writing room.
You can now define which Slices should be included in the Custom Type SliceZone.
Pushing the Custom Type to Prismic will also save and push all linked Slices.

To customise Custom Types thumbnails, create an index.png file in each CT folder eg. customtypes/homepage/index.png.

If you are connected to your Prismic API endpoint when you loaded this page, your existing custom types
will be downloaded and saved in your project. Check it out!

New design 🖼

We rethought the SliceMachine UI/UX to make it clearer and simpler to use.

So we reshaped the tool with:

• A more intuitive way to add and edit fields in Slices and Custom Types
• A new navigation to switch between Custom Types and Slices whenever you want

We hope you will like this new interface. If you find some improvements or have suggestions, don't hesitate to contact us.

Also

• We added the (much-requested) Content Relationship field
• We added the Link to Media field
• Storybook is now optional
• Libraries index files (eg. slices/index.js) are now regenerated after each save
• Generated mocks and stories are now stored in .slicemachine/assets
• Various fixes, a bit more stability

Migration

When you launch the new builder, we run a migration over your content: all mocks and stories
will be moved to .slicemachine/assets. This may break the first render of Storybook. If that's the case
for you, try to manually save Slices that have any issue. If your mocks & stories aren't modified between saves,
check that the files have been correctly migrated.

@Slicemachine/init V1.0.0

@slicemachine/[email protected]

@slicemachine/[email protected]

@Slicemachine/core V1.0.0

@slicemachine/[email protected]

@slicemachine/[email protected]