From 205b49c04ddc04924a610be999b2c752e208eaa4 Mon Sep 17 00:00:00 2001 From: Artur Arseniev Date: Thu, 20 Sep 2018 08:20:29 +0200 Subject: [PATCH] Update docs --- docs/guides/Custom-CSS-parser.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/guides/Custom-CSS-parser.md b/docs/guides/Custom-CSS-parser.md index 5206bfdd7..917527e46 100644 --- a/docs/guides/Custom-CSS-parser.md +++ b/docs/guides/Custom-CSS-parser.md @@ -5,6 +5,10 @@ title: Use Custom CSS Parser If you just use GrapesJS for building templates from scratch, so you start from an empty canvas and for editing you strictly rely on the generated JSON (final HTML/CSS only for end-users) then, probably, you might skip this guide. On the other hand, if you import templates from already defined HTML/CSS or let the user embed custom codes (eg. using the [grapesjs-custom-code](https://github.com/artf/grapesjs-custom-code) plugin), then you have to know that you might face strange behaviors. +::: warning +This guide requires GrapesJS v0.14.33 or higher +::: + [[toc]]