GrapesJS out in the wild
Question
Hi,
I wanted to check out some examples of how people are using GrapesJS and how they may have extended it or customized it to their needs.
Would be cool if anyone with a public facing (I guess even a screenshot) site commented on this issue to build a list of current uses of this great extension!
Answers (3)
We use GrapesJS to power our CMS at http://saasquatch.com
Widgets
- GrapesJS powers the editing of the content in our in-app javascript widget
- We have customized most of the toolbars, removed most of the default components, and have it made up of only custom web components
- Plugged in https://cloudinary.com/ for asset management
- It works pretty great with Web Components and https://stenciljs.com/ ❤️
- Recommendation: Use GrapesJS with Web Components

Emails
- We also use it for HTML email editing, but find that it isn't great (because HTML emails are a nightmare to get right, not directly a fault of GrapesJS....) We're looking to switch to GrapesJS + MJML or https://beefree.io/ to make the end-user experience more bearable.
- Recommendation: Avoid GrapesJS for plain HTML email templates

My project has finally been released, so I can show it off now:

It's part of our tabletop RPG battlemap editor DungeonFog and used for creating notes and adventure books for game masters. The idea is that you can print them to PDF from the browser, so it's kinda like a simpler InDesign.
We're upgrading to GrapesJS for our Landing Page and Email designers in DailyStory.
We made quite a few changes, mostly to turn-off or disable certain functionality while also writing all new components from the ground-up so we could control the editing experience (we limit what you can/cannot do in the designer), e.g. where blocks and components can be placed.
And, all the landing page components are built around Bootstrap. Just keeps things super-simple for our customers.

We then had to start from scratch and write another set of components / blocks from the ground up for email templating with tables to work in an email-friendly way while controlling what could/could not be done in the editor. We needed different types of components for different situations, e.g. a non-editable/removable layout container table vs. a draggable content section table.

We also integrated our own file manager.

We're launching our landing page editor to our customers in 2 weeks (still putting the finishing touches on it). We're planning to launch our updates to the email editor in late July. We started both these projects about 9 months ago (worked on them on-and-off). I'll share some screen shots of the email editor later.
Great project @artf
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1356
Add "Insert" button to assets manager
How would you go about adding a "Insert image" button to the assets manager modal? At the moment the "Add Image" may be confusing to some w...
Issue #644
Upgrade to Fontawesome 5
From fontawesome 4. Would be a good opportunity to make fa5 a peer-dependency this time as well, so people aren't including it twice Some i...
Issue #2038
Buttons flashing with question mark and non responsive.
Hi, I'm having issues using this library, firstly some buttons are missing their icons and are flashing when clicking on them they are not...
Issue #2065
Few Questions
First of all, Amazing project thumbs up to everybody involved. I have a couple of questions:How can I iterate over all of the components an...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.