From 897692b7b5163a24558bca564e8d5678baece369 Mon Sep 17 00:00:00 2001 From: jonniebigodes Date: Fri, 26 Mar 2021 22:13:38 +0000 Subject: [PATCH] Merge pull request #14359 from storybookjs/fix_docs_new_frameworks_link Chore: (Docs) fixes broken link in GH for new framework docs --- docs/api/new-frameworks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/new-frameworks.md b/docs/api/new-frameworks.md index 193de1a6f743..ff222c29f9ea 100644 --- a/docs/api/new-frameworks.md +++ b/docs/api/new-frameworks.md @@ -24,7 +24,7 @@ Supporting a new framework in Storybook typically consists of two main aspects: ## Configuring the server -Storybook has the concept of [presets](../addons/writing-presets#presets-api), which are typically babel/webpack configurations for file loading. If your framework has its own file format, e.g. “.vue,” you might need to transform these files into JS files at load time. If you expect every user of your framework to need this, you should add it to the framework. So far every framework added to Storybook has done this, because Storybook’s core configuration is very minimal. +Storybook has the concept of [presets](../addons/writing-presets.md#presets-api), which are typically babel/webpack configurations for file loading. If your framework has its own file format, e.g. “.vue,” you might need to transform these files into JS files at load time. If you expect every user of your framework to need this, you should add it to the framework. So far every framework added to Storybook has done this, because Storybook’s core configuration is very minimal. ### Package structure