GrapesJS out in the wild

[chrisedington]

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!

[arthuralmeidap]

Unfortunately, I can disclosure the app built on top of GrapesJS, but I have been working on an UI tool to build E-mail marketing. We have a lot of customizations/integrations to improve the existing greatness of GrapesJS like creating a custom Asset Manager; Social blocks (to add social medias to the email);

[tristanMatthias]

I'm using in Origami CMS!

[artf]

@tristanMatthias wow! seems quite promising 👏

[tristanMatthias]

Thanks @artf! I need a lot of help 😅

[noogen]

Still a WIP, I'm using it to build new form components: https://niiknow.github.io/grapesjs-components-farmer/

Mainly focus on getting unique Name field, which are important for Form submission. Also implement doTjs for templating, so I can work on supporting additional CSS framework with initial support of Bootstrap4.

[artf]

@noogen great, thanks for sharing

[loganvolkers]

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

[artf]

Amazing work @loganvolkers thanks for pointing out your use cases

[gabrigcl]

I'm using grapesjs as the core of our online ebook creator SaiteBooker: www.saitebooker.com.br. It's still in development and this public version is a prototype.

[artf]

@gabrigcl fantastic use case 👏

[trafalmejo]

Hi Guys,

I am using Grapesjs to help people to create GUIs to control interactive installations:
OSCAR create responsive and beauty GUIs to control your installations

[lcsdms]

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

Looks like there's a new one for MJML available: https://grapesjs.com/demo-mjml.html (https://github.com/artf/grapesjs-mjml)

[edvinasba1]

@froderf May we see some screenshots or maybe a demo?

[robhoward]

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